SAML Single Sign On <= 5.4.3 - Unauthenticated Authentication Bypass via 'SAMLResponse' Parameter Signature Algorithm Confusion
Strategic Overview
- Status
- Patched in 5.4.4
- Affected Plugin
- SAML Single Sign On – SSO Login
- Affected Version
<= 5.4.3- CVSS
- 9.8Critical
- Weakness type
- CWE-347 · Improper Verification of Cryptographic Signature
- CVE
CVE-2026-15013
At a glance
CVE-2026-15013 is a critical-severity Improper Verification of Cryptographic Signature vulnerability in the SAML Single Sign On WordPress plugin, affecting versions <= 5.4.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.4.4; sites on affected versions should update now. Disclosed July 2026, reported by lhking.
Vulnerability Overview
The SAML Single Sign On – SSO Login plugin for WordPress is vulnerable to Authentication Bypass via SAML Signature Algorithm Confusion in all versions up to, and including, 5.4.3. The vulnerability exists because `Mo_SAML_Utilities::mo_saml_cast_key()` reads the `SignatureMethod` Algorithm attribute directly from the attacker-controlled `SAMLResponse` parameter rather than enforcing the locally configured algorithm, causing the plugin to recast the IdP's RSA public key as an HMAC-SHA1 shared secret and validate the forged signature against it. This makes it possible for unauthenticated attackers to forge a SAML assertion targeting any WordPress account — including administrators — obtain valid WordPress authentication cookies, and achieve full administrator-level account takeover.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-347: Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
Remediation
Update to version 5.4.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: SAML Single Sign On 5.4.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in SAML Single Sign On – SSO Login
- 9.8CVE-2026-61979: SAML Single Sign On – SSO Login Privilege Escalation
CVE-2026-61979 - 9.8CVE-2026-15981: SAML Single Sign On <= 5.4.4 Authentication Bypass
CVE-2026-15981 - 8.8SAML Single Sign On – SAML SSO Login <= 4.8.75 CSRF
- 7.5CVE-2026-75807: SAML Single Sign On <= 5.4.6 Authentication Bypass
CVE-2026-75807 - 7.3CVE-2026-19842: SAML Single Sign On Privilege Escalation
CVE-2026-19842 - 6.1CVE-2022-4496: SAML Single Sign On Open Redirect
CVE-2022-4496 - 6.1SAML Single Sign On – SAML SSO Login <= 4.9.20 Reflected XSS
- 6.1CVE-2020-6850: SAML Single Sign On – SAML SSO Login <= 4.8.83 XSS
CVE-2020-6850
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C