Pheditor is a single-file editor and file manager written in PHP. Prior to version 2.0.5, there is an authenticated terminal command whitelist bypass. The terminal feature checks whether the submitted command starts with one of the configured TERMINAL_COMMANDS values, then passes the full command string to shell_exec(). Shell command substitution such as $() is not blocked, so an authenticated user with the terminal permission can bypass a restricted command allowlist and execute arbitrary shell commands as the web server user. This issue has been patched in version 2.0.5.
CVE-2026-54540
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 56(Track*)EG Risk 56/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 27, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026Authenticated terminal command whitelist bypass in Pheditor · Advisory · pheditor/pheditor · GitHub
https://github.com/pheditor/pheditor/security/advisories/GHSA-9643-6xjp-vx57Pheditor 2.0.5
Patch available: pheditor/pheditor 2.0.5
https://github.com/pheditor/pheditor/releases/tag/2.0.5Vendor Advisories for CVE-2026-54540(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pheditor/pheditor | 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 | 2.0.5 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 19:42 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 19:34 UTCEG score recompute
- 2026-07-27 19:08 UTCEG score recompute
- 2026-07-27 18:24 UTCEG score recompute
- 2026-07-26 11:24 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-16 20:04 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-54540?
When was CVE-2026-54540 disclosed?
Is CVE-2026-54540 actively exploited?
What is the CVSS score of CVE-2026-54540?
How do I remediate CVE-2026-54540?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54540
Is Your Infrastructure Affected by CVE-2026-54540?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.