OS Command Injection in pheditor/pheditor (CVE-2026-48030)
Summary
OS command injection in pheditor/pheditor (CVE-2026-48030). Successful exploitation can lead to full system takeover. Exploitable via command. Mitigation: upgrade to 2.0.4 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.4, an OS Command Injection vulnerability in the terminal action handler allows any authenticated user to execute arbitrary OS commands by injecting shell metacharacters into the 'dir' POST parameter, completely bypassing the TERMINAL_COMMANDS whitelist and achieving full Remote Code Execution with web server privileges. This issue has been patched in version 2.0.4.
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-48030 has been found in pheditor/pheditor.
Attackers can target a specific entry point like command over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade pheditor/pheditor to 2.0.4 or later.
If unsure, ask your IT team or search "pheditor/pheditor CVE-2026-48030" on the vendor's site.
CVE-2026-48030 (pheditor/pheditor) — CWE-78 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: command / dir
Patched: 2.0.4 — 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.
OS command injection (CWE-78) exists in pheditor/pheditor. Attackers reach the vulnerable code path via command.
Check the vendor advisory for the affected versions of pheditor/pheditor. Attack surface: command / dir.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 2.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'pheditor/pheditor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pheditor/pheditorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pheditor/pheditor to 2.0.4ステージング環境で 2.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com