Categories
CVE-2026-42569 critical CVSS 9.4

Vulnerability in nabeel/phpvms (CVE-2026-42569)

Summary

Vulnerability in nabeel/phpvms (CVE-2026-42569). Data can be tampered with by attackers. Mitigation: upgrade to 7.0.6 or later.

Original description

The description as published by the source.

phpVMS is a PHP application to run and simulate an airline. Prior to version 7.0.6, a critical vulnerability in phpVMS allowed unauthenticated access to a legacy import feature. This issue has been patched in version 7.0.6.

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-42569 has been found in nabeel/phpvms.
Data can be tampered with by attackers. CVSS score: 9.4/10.
What to do: upgrade nabeel/phpvms to 7.0.6 or later.
If unsure, ask your IT team or search "nabeel/phpvms CVE-2026-42569" on the vendor's site.

CVE-2026-42569 (nabeel/phpvms) — CWE-284 / CVSS v3 9.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.0.6 — 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

A vulnerability (CWE-284) exists in nabeel/phpvms.

📍 Affected scope

Check the vendor advisory for the affected versions of nabeel/phpvms.

🔥 Severity

Severity: Critical (CVSS 9.4/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 7.0.6.

🛡️ 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 'nabeel/phpvms' . 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 'nabeel/phpvms' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade nabeel/phpvms to 7.0.6

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

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

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

Affected packages

composer nabeel/phpvms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.6"}]}]
Packagist nabeel/phpvms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.6"}]}]

References

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