Pheditor: Authentication Bypass in Forced Password-Change Flow via Unverified Current Password
Affects pheditor/pheditorSource GCVE Database
CVSS 10.0 Critical · fixed in 2.0.8 : patch pheditor/pheditor as a priority.
Data as of 07/25/2026, 23:51:25 UTC
- Patch
- Available – fixed in 2.0.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistpheditor/pheditor | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Pheditor version 2.0.8 and later. The vulnerability is remediated by verifying the submitted current password against the stored password hash before allowing the forced password-change flow. Users should upgrade to version 2.0.8 or later to address this issue. Until patched, do not leave the default password in use. Patch status is confirmed by the affectedVersions field indicating versions prior to 2.0.8 are vulnerable.
Description
Pheditor versions prior to 2.0.8 contain an authentication bypass vulnerability in the forced password-change flow triggered when the stored password is still the default ('admin'). The vulnerability allows an unauthenticated attacker to set an arbitrary new admin password and gain an authenticated session without knowing the current password. This occurs because the submitted current password is not verified before allowing the password change. The issue is critical due to complete authentication bypass and full administrative access.
Impact
An unauthenticated attacker can fully bypass authentication on affected Pheditor instances that still use the default 'admin' password. The attacker can arbitrarily set a new admin password and obtain an authenticated session, gaining full administrative control. This vulnerability is critical as it allows complete compromise of the affected system without any prior credentials.
Summary
The forced password-change flow in Pheditor (before version 2.0.8) does not verify that the submitted current password matches the stored password when the stored password is still the default ('admin'). Any non-empty value submitted as the current password allows access to the password-change form. Submitting new password fields in the same request sets a new admin password and authenticates the attacker without proof of knowledge of the original password. The root cause is a missing verification step comparing the submitted password hash to the stored password hash before entering the forced password-change logic. This flaw enables a complete authentication bypass on instances that have not changed the default password.
Weaknesses
- CWE-1392Use of Default Credentials (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
References
- github.com/pheditor/pheditor/security/advisories/GHSA-f25v-x6vr-962g (opens in a new tab)
- github.com/pheditor/pheditor/commit/0978bcda644832b67357340e2f271e32d86fdf86 (opens in a new tab)
- github.com/pheditor/pheditor (opens in a new tab)
- github.com/pheditor/pheditor/releases/tag/2.0.8 (opens in a new tab)