SAML Single Sign On <= 5.4.6 - Unauthenticated Authentication Bypass via X.509 Certificate Poisoning
Strategic Overview
- Status
- Patched in 5.4.7
- Affected Plugin
- SAML Single Sign On – SSO Login
- Affected Version
<= 5.4.6- CVSS
- 7.5High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-75807
At a glance
CVE-2026-75807 is a high-severity Improper Authentication vulnerability in the SAML Single Sign On WordPress plugin, affecting versions <= 5.4.6. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.4.7; sites on affected versions should update now. Disclosed August 2026, reported by Tanishq Shah.
Vulnerability Overview
The SAML Single Sign On – SSO Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 5.4.6. This is due to the mo_saml_login_validate() ACS handler persisting the X.509 certificate extracted from an incoming SAMLResponse into the mo_saml_required_certificate option before the signature-validation verdict is enforced, because mo_saml_find_certificate() returns false on a fingerprint mismatch rather than halting execution. This makes it possible for unauthenticated attackers to overwrite the plugin's stored IdP signing certificate with an attacker-controlled value, and subsequently forge SAML assertions for any WordPress account — including administrators — to obtain a fully privileged session. Note: The exploit requires the administrator to perform a repair after receiving the test_config_error_wpsamlerr004 error message during the test configuration.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
SAML Single Sign On <= 5.4.6 carries this weakness at mo_saml_login_validate(), and reaching it takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For SAML Single Sign On the fix is 5.4.7: builds <= 5.4.6 are affected, anything from 5.4.7 onward is not.
Remediation
Update to version 5.4.7, 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.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
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-15013: SAML Single Sign On <= 5.4.3 Authentication Bypass
CVE-2026-15013 - 8.8SAML Single Sign On – SAML SSO Login <= 4.8.75 CSRF
- 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 - 6.1CVE-2019-12346: SAML Single Sign On – SAML SSO Login < 4.8.73 XSS
CVE-2019-12346
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C