VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

SAML Single Sign On <= 5.4.6 — Unauthenticated Authentication Bypass via X.509 Certificate Poisoning

CVE-2026-75807Published · Updated

Action summary

Affected: ≤5.4.6Update to 5.4.7 or newer

All remediation steps
Watch plugin
Severity
High7.5
CVSS
7.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:H Attack complexity
High
PR:N Privileges required
None
UI:R User interaction
Required
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-287 Improper Authentication
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

SAML Single Sign On – SSO Login miniorange-saml-20-single-sign-on

  1. Affected≤ 5.4.6
  2. Patched in5.4.7

Update to 5.4.7 or newer.

You are affected if you run ≤ 5.4.6. Version 5.4.7 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under SAML Single Sign On – SSO Login.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 5.4.7, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch SAML Single Sign On – SSO Login to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Tanishq Shah, Thatchapol Booranatanit (AliceZz).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in SAML Single Sign On – SSO Login

All 13
More vulnerabilities in SAML Single Sign On – SSO Login
SeverityVulnerabilityCVEPublished
High7.5Unauthenticated Denial of Service
≤6.1.0Update to 6.2.0
CVE-2026-62126
High7.3Unauthenticated Privilege Escalation
≤5.4.7Update to 6.0.0
CVE-2026-82842
High7.3Unauthenticated Privilege Escalation
4.8.85 – 5.4.6Update to 5.4.7
CVE-2026-19842
Critical9.8Unauthenticated Privilege Escalation
≤5.4.3Update to 5.4.4
CVE-2026-61979
Critical9.8Unauthenticated Authentication Bypass via SAMLResponse Parameter
≤5.4.4Update to 5.4.5
CVE-2026-15981

Timeline

  1. CVE published

    Severity high, CVSS 7.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?