Skip to content
Web

CVE-2026-55579

9.8
Critical
EPSS 0.60%Patch availableJul 28, 2026

Hardcoded default admin password in Pheditor <=2.0.5 enables full access and RCE.

common questions

Is CVE-2026-55579 being exploited?

Not confirmed. CVE-2026-55579 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.60% probability of exploitation in the next 30 days.

How severe is CVE-2026-55579?

CVE-2026-55579 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55579?

Yes. A fix has been recorded for CVE-2026-55579. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55579 affect?

CVE-2026-55579 affects Pheditor 2.0.1 - 2.0.5, deployments using pheditor.php single-file install, web servers hosting Pheditor. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55579?

Upgrade to Pheditor 2.0.6, change default credentials, audit deployments and logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Pheditor 2.0.1 - 2.0.5deployments using pheditor.php single-file installweb servers hosting Pheditor
impact

Default hardcoded 'admin' creds grant full admin access, enabling arbitrary file read/write, file upload abuse and remote code execution via editor/terminal.

action required

Immediate action required

affected versions
pheditor pheditor
  • affected>= 2.0.1 and < 2.0.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free