Skip to content
Web

CVE-2026-15013

CRITICAL
Critical
EPSS 2%Jul 16, 2026

Auth bypass in WordPress SAML SSO plugin allows admin takeover.

common questions

Is CVE-2026-15013 being exploited?

Not confirmed. CVE-2026-15013 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.5% probability of exploitation in the next 30 days.

How severe is CVE-2026-15013?

CVE-2026-15013 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15013?

Not known from our data. No patch reference has been recorded for CVE-2026-15013, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-15013 affect?

CVE-2026-15013 affects WordPress SAML Single Sign On – SSO Login plugin <= 5.4.3, WordPress sites using the SAML SSO Login plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15013?

Disable SAML plugin or block SAML logins; apply vendor patch when released; audit admin logins.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress SAML Single Sign On – SSO Login plugin <= 5.4.3WordPress sites using the SAML SSO Login plugin
impact

Attackers can forge SAML assertions to obtain valid auth cookies and gain full administrator account takeover remotely.

action required

Immediate action required

affected versions
cyberlord92 SAML Single Sign On – SSO Login
  • affected<= 5.4.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free