CVE-2026-15013

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-16. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
33.9%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 16, 2026

References (7)

Vendor Advisories for CVE-2026-15013(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 06:03 UTCGHSA enrichment
  10. 2026-07-17 01:48 UTCGHSA enrichment
  11. 2026-07-16 21:32 UTCGHSA enrichment
  12. 2026-07-16 17:16 UTCGHSA enrichment
  13. 2026-07-16 17:02 UTCEPSS rescore
  14. 2026-07-16 13:00 UTCGHSA enrichment
  15. 2026-07-16 08:44 UTCGHSA enrichment
  16. 2026-07-16 04:29 UTCEG score recompute
  17. 2026-07-16 04:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15013?
CVE-2026-15013 is a critical vulnerability published on July 16, 2026. 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 MoSAMLUtilities::mosamlcast_key() reads the SignatureMethod Algorithm attribute…
When was CVE-2026-15013 disclosed?
CVE-2026-15013 was first published in the National Vulnerability Database on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15013 actively exploited?
CVE-2026-15013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15013?
CVE-2026-15013 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-15013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15013, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15013

Explore →

Is Your Infrastructure Affected by CVE-2026-15013?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs