Vulnerability in pheditor/pheditor (CVE-2026-55579)
Summary
Vulnerability in pheditor/pheditor (CVE-2026-55579). Successful exploitation can lead to full system takeover. Exploitable via admin. Mitigation: upgrade to 2.0.6 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.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.
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-55579 has been found in pheditor/pheditor.
Attackers can target a specific entry point like admin over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade pheditor/pheditor to 2.0.6 or later.
If unsure, ask your IT team or search "pheditor/pheditor CVE-2026-55579" on the vendor's site.
CVE-2026-55579 (pheditor/pheditor) — CWE-798 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: admin / e538f05b6faec99e5b23726bc9c17d6b57774297 / main / PASSWORD_BCRYPT
Patched: 2.0.6 — 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.
A vulnerability (CWE-798) exists in pheditor/pheditor. Attackers reach the vulnerable code path via admin without authentication.
Check the vendor advisory for the affected versions of pheditor/pheditor. Attack surface: admin / e538f05b6faec99e5b23726bc9c17d6b57774297 / main / PASSWORD_BCRYPT.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2.0.6.
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.6ステージング環境で 2.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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