CVE-2026-15013: SAML Single Sign On <= 5.4.3 - Unauthenticated Authentication Bypass via 'SAMLResponse' Parameter Signature Algorithm Confusion
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.
Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress SAML SSO plugin can let an unauthenticated attacker log in as any WordPress user, including an administrator. The issue comes from trusting a signature algorithm value supplied inside the SAML response. That can turn identity-provider public-key validation into attacker-controlled HMAC validation.
Executive priority
Treat this as urgent for any WordPress site using the affected plugin. A successful attack could give full administrative control of the site without credentials.
Technical view
The plugin up to 5.4.3 reads the SAMLResponse SignatureMethod Algorithm and recasts the IdP RSA public key as an HMAC-SHA1 secret. This algorithm-confusion flaw can allow forged SAML assertions to pass validation and issue valid WordPress authentication cookies.
Likely exposure
Exposure is likely limited to WordPress sites using SAML Single Sign On – SSO Login versions up to and including 5.4.3, especially where SAML login is internet-accessible.
Exploitation context
The CVE describes unauthenticated remote account takeover with no user interaction. The source bundle does not show CISA KEV listing or confirmed active exploitation, so active exploitation should not be assumed.
Researcher notes
Evidence points to CWE-347 signature verification failure through algorithm confusion. The provided sources identify vulnerable code paths and a related changeset, but the bundle does not explicitly name a fixed version or confirmed exploitation.
Mitigation direction
Identify all WordPress sites using the affected plugin.
Check vendor or WordPress.org guidance for a fixed release beyond 5.4.3.
Temporarily disable the plugin where update status cannot be confirmed.
Review administrator accounts and active sessions after remediation.
Rotate privileged WordPress credentials if compromise is suspected.
Validation and detection
Inventory plugin name and version across WordPress environments.
Confirm whether any site runs version 5.4.3 or earlier.
Review SAML login exposure on public WordPress routes.
Check logs for unexpected admin logins or new privileged users.
Verify authentication behavior after applying vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-347 · source CWE mapping
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.