CVE-2026-55579: Pheditor hardcoded default password in pheditor.php

CVE-2026-55579 · Severity: critical · CVSS 9.8 · Published 2026-07-27

Pheditor, a web-based file management and code editing tool, contains a hardcoded default password that is publicly known. Because the software does not force users to change this password upon first use, attackers can easily gain full administrative control over the application. This allows unauthorized individuals to read sensitive files, upload malicious software, and execute arbitrary commands on the underlying server, potentially leading to a complete system takeover.

Technologies: pheditor/pheditor (Packagist), Pheditor. Vendors: Packagist, Pheditor.

Quick answers

Is CVE-2026-55579 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-55579 being exploited in the wild.
How severe is CVE-2026-55579?
Critical severity, with a CVSS score of 9.8, published 27 July 2026.
Which products and versions are affected?
pheditor/pheditor (Packagist) >= 2.0.1, < 2.0.6, ECOSYSTEM:introduced=2.0.1,fixed=2.0.6; Pheditor >= 2.0.1, < 2.0.6.
Is there a fix for CVE-2026-55579?
Yes. pheditor/pheditor (Packagist): upgrade to 2.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55579 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-55579?
Check whether you run pheditor/pheditor (Packagist) or Pheditor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • pheditor/pheditor (Packagist): upgrade to 2.0.6 or later
    composer require pheditor/pheditor:^2.0.6

Technical details

Pheditor (v2.0.1 to <2.0.6) utilizes a hardcoded SHA-512 hash for the default password 'admin' stored directly in the pheditor.php source file. The application lacks a setup wizard or a forced password change mechanism, meaning many deployments remain accessible via these default credentials. An unauthenticated attacker can use these credentials to access the built-in terminal and file upload features. By combining the default credentials with the application's legitimate administrative functionality, an attacker can achieve arbitrary file read/write and remote code execution (RCE). Version 2.0.6 addresses this by implementing a secure password change mechanism and strengthening command validation.

Affected products

  • pheditor Pheditor >= 2.0.1, < 2.0.6

Identifiers

  • CVE-2026-55579
  • GHSA-p4h7-p9rj-2pq2

Timeline

  • 2026-06-14: patched: Version 2.0.6 released to address the issue.
  • 2026-07-27: advisory: CVE-2026-55579 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.