CVE-2026-55579

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pheditor is a single-file editor and file manager written in PHP. From version 2.0.1 to before version 2.0.6, Pheditor ships with a hardcoded default password admin (SHA-512 hash stored at pheditor.php:11). There is no mechanism to force a password change on first login. Any deployment using the default credentials grants an attacker full access to the file editor, file upload, and terminal features, enabling arbitrary file read/write and remote code execution. This issue has been patched in version 2.0.6.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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 computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 27, 2026

Advisory Details (2)

Auto-updated Jul 27, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Hardcoded default password 'admin' with no forced change enables full application compromise · Advisory · pheditor/pheditor · GitHub

https://github.com/pheditor/pheditor/security/advisories/GHSA-p4h7-p9rj-2pq2
github_release Patch Available

Pheditor 2.0.6

Patch available: pheditor/pheditor 2.0.6

https://github.com/pheditor/pheditor/releases/tag/2.0.6

Vendor Advisories for CVE-2026-55579(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)
PackageVulnerable rangeFixed inDependents
pheditor/pheditor2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.52.0.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 8× 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.

  1. 2026-07-28 17:09 UTCEG score recompute
  2. 2026-07-28 15:37 UTCEPSS rescore
  3. 2026-07-27 20:45 UTCEG score recompute
  4. 2026-07-27 19:21 UTCEG score recompute
  5. 2026-07-27 18:24 UTCEG score recompute
  6. 2026-07-26 11:24 UTCEG score recompute
  7. 2026-07-23 03:20 UTCEG score recompute
  8. 2026-07-16 20:21 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55579?
CVE-2026-55579 is a critical vulnerability published on July 16, 2026. Pheditor is a single-file editor and file manager written in PHP. From version 2.0.1 to before version 2.0.6, Pheditor ships with a hardcoded default password admin (SHA-512 hash stored at pheditor.php:11). There is no mechanism to force a password change on first login. Any deployment using the…
When was CVE-2026-55579 disclosed?
CVE-2026-55579 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55579 actively exploited?
CVE-2026-55579 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55579?
CVE-2026-55579 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-55579?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55579, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55579

Explore →

Is Your Infrastructure Affected by CVE-2026-55579?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs