Categories
CVE-2026-55578 high CVSS 8.8

OS Command Injection in pheditor/pheditor (CVE-2026-55578)

Summary

OS command injection in pheditor/pheditor (CVE-2026-55578). Successful exploitation can lead to full system takeover. Exploitable via terminal. Mitigation: upgrade to 2.0.6 or later.

Original description

The description as published by the source.

Pheditor is a single-file editor and file manager written in PHP. From version 2.0.1 to before version 2.0.6, the terminal feature in Pheditor uses an incomplete character blocklist to sanitize user-supplied commands before passing them to shell_exec(). After the fix for GHSA-9643-6xjp-vx57 (which added $ to the blocklist), the characters | (single pipe), ` (backtick), and the newline byte (0x0A) remain unblocked. An authenticated user with the terminal permission (enabled by default) can leverage any of these to bypass the TERMINAL_COMMANDS allowlist and execute arbitrary OS commands as the web server user. This issue has been patched in version 2.0.6.

Source: GitHub Security Advisories (Global) 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-55578 has been found in pheditor/pheditor.
Attackers can target a specific entry point like terminal over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade pheditor/pheditor to 2.0.6 or later.
If unsure, ask your IT team or search "pheditor/pheditor CVE-2026-55578" on the vendor's site.

CVE-2026-55578 (pheditor/pheditor) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: terminal / TERMINAL_COMMANDS / e538f05b6faec99e5b23726bc9c17d6b57774297 / main
Patched: 2.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

OS command injection (CWE-78) exists in pheditor/pheditor. Attackers reach the vulnerable code path via terminal.

📍 Affected scope

Check the vendor advisory for the affected versions of pheditor/pheditor. Attack surface: terminal / TERMINAL_COMMANDS / e538f05b6faec99e5b23726bc9c17d6b57774297 / main.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.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 'pheditor/pheditor' . 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 'pheditor/pheditor' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade pheditor/pheditor to 2.0.6

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

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

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

Affected packages

composer pheditor/pheditor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.6"}]}]
Packagist pheditor/pheditor
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.1"},{"fixed":"2.0.6"}]}]

References

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