Categories
CVE-2026-42549 medium CVSS 4.4

Path Traversal in flightphp/core (CVE-2026-42549)

Summary

Path traversal in flightphp/core (CVE-2026-42549). Risk of unauthorized operations or information disclosure. Exploitable via b8dd23a. Mitigation: upgrade to 3.18.1 or later.

Original description

The description as published by the source.

Flight is an extensible micro-framework for PHP. Prior to 3.18.1, the make:controller CLI command calls mkdir(..., recursive: true) on a path built from the user-supplied controller name, before Nette's class-name validation runs. The class-file write is correctly rejected by Nette when the name contains /, but the recursive directory creation side effect is already committed — including directories located outside the project root through ../ traversal. This vulnerability is fixed in 3.18.1.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-42549 has been found in flightphp/core.
Attackers can target a specific entry point like b8dd23a over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade flightphp/core to 3.18.1 or later.
If unsure, ask your IT team or search "flightphp/core CVE-2026-42549" on the vendor's site.

CVE-2026-42549 (flightphp/core) — CWE-22 / CVSS v3 4.4
Attack vector: local / no user interaction
Attack surface: b8dd23a / mkdir
Patched: 3.18.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in flightphp/core. Attackers reach the vulnerable code path via b8dd23a.

📍 Affected scope

Check the vendor advisory for the affected versions of flightphp/core. Attack surface: b8dd23a / mkdir.

🔥 Severity

Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.18.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flightphp/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'flightphp/core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で flightphp/core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade flightphp/core to 3.18.1

    ステージング環境で 3.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer flightphp/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.18.1"}]}]
Packagist flightphp/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.18.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details