CVE-2025-54336: Plesk Obsidian · Incorrect Comparison
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, European organizations should immediately upgrade Plesk Obsidian to a patched version once released by the vendor. In the interim, administrators should implement strict password policies avoiding passwords that start with "0e" followed by digits to prevent triggering the flawed comparison. Additionally, reviewing and modifying the authentication code to use strict comparison operators (===) instead of loose equality (==) is essential to prevent type juggling vulnerabilities. Organizations should also enable multi-factor authentication (MFA) for Plesk admin accounts to add an additional security layer. Monitoring login attempts and setting up alerts for suspicious activities can help detect exploitation attempts early. Network-level protections such as restricting access to the Plesk admin interface via IP whitelisting or VPNs can reduce exposure. Regular security audits and penetration testing focusing on authentication mechanisms will help identify similar weaknesses. Finally, educating administrators about this vulnerability and secure coding practices can prevent recurrence.
Description
In Plesk Obsidian 18.0.70, _isAdminPasswordValid uses an == comparison. Thus, if the correct password is "0e" followed by any digit string, then an attacker can login with any other string that evaluates to 0.0 (such as the 0e0 string). This occurs in admin/plib/LoginManager.php.