CVE-2026-15013

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-44866 (ENISA EUVD) · GHSA-p847-q8vx-c3fg (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

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

The CVE record's CNA (Wordfence) lists cyberlord92 SAML Single Sign On – SSO Login versions up to and including 5.4.3 as affected. No release containing a fix is confirmed on record.

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
2.4%
EPSS %ILE
84th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Oct 16, 2026
🔬 Proof of concept available. No fix on record yet.
Web page🟡 PoC Available

Full Disclosure: CVE-2026-15013 – miniOrange SAML SSO <= 5.4.3 Unauthenticated Authentication Bypass (PoC)

http://seclists.org/fulldisclosure/2026/Aug/33

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 22× in last 7d / 72× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 402 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 302 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 20:22 UTCEG score recompute
  2. 2026-10-29 20:22 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-29 16:32 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  4. 2026-10-28 20:28 UTCEG score recompute
  5. 2026-10-28 20:28 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  7. 2026-10-27 20:33 UTCEG score recompute
  8. 2026-10-27 20:33 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  10. 2026-10-26 20:38 UTCEG score recompute
  11. 2026-10-26 20:38 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-26 16:30 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  13. 2026-10-25 18:51 UTCEG score recompute
  14. 2026-10-25 18:51 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-25 16:32 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  16. 2026-10-25 14:47 UTCEG score recompute
  17. 2026-10-24 18:47 UTCEG score recompute
  18. 2026-10-24 18:47 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  20. 2026-10-23 18:53 UTCEG score recompute
  21. 2026-10-23 18:53 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  23. 2026-10-22 18:58 UTCEG score recompute
  24. 2026-10-22 18:58 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.5% · 74th percentile
Show 75 more
  1. 2026-10-21 19:04 UTCEG score recompute
  2. 2026-10-21 19:04 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  4. 2026-10-20 19:07 UTCEG score recompute
  5. 2026-10-20 19:06 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  7. 2026-10-19 19:09 UTCEG score recompute
  8. 2026-10-19 19:09 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-10-18 19:13 UTCEG score recompute
  11. 2026-10-18 19:13 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-10-18 05:01 UTCEG score recompute
  14. 2026-10-17 19:18 UTCEG score recompute
  15. 2026-10-17 19:18 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  17. 2026-10-16 19:23 UTCEG score recompute
  18. 2026-10-16 19:23 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-16 16:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  20. 2026-10-15 16:59 UTCEG score recompute
  21. 2026-10-15 16:58 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  23. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  24. 2026-10-14 10:59 UTCEG score recompute
  25. 2026-10-14 10:58 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  27. 2026-10-13 09:38 UTCEG score recompute
  28. 2026-10-13 09:38 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  30. 2026-10-12 16:33 UTCEG score recompute
  31. 2026-10-12 09:40 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-11 20:10 UTCEG score recompute
  33. 2026-10-11 17:22 UTCEG score recompute
  34. 2026-10-11 14:55 UTCEG score recompute
  35. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  36. 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  37. 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  38. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  39. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  40. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  41. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  42. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  43. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  44. 2026-10-01 15:54 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-01 11:30 UTCEG score recompute
  46. 2026-10-01 11:30 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  48. 2026-09-29 15:20 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  49. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  50. 2026-09-28 13:14 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-09-28 08:39 UTCEG score recompute
  52. 2026-09-28 08:39 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-09-27 13:47 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  54. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  55. 2026-09-24 13:17 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-24 08:38 UTCEG score recompute
  57. 2026-09-24 08:38 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-23 11:41 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-09-23 07:25 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-23 03:10 UTCEG score recompute
  61. 2026-09-23 03:10 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  63. 2026-09-18 09:59 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-18 04:40 UTCEG score recompute
  65. 2026-09-18 04:40 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  67. 2026-09-16 05:14 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  68. 2026-09-14 12:21 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-14 07:40 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-14 03:25 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-13 23:10 UTCEG score recompute
  72. 2026-09-13 23:10 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-13 16:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  74. 2026-09-13 16:24 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-13 11:47 UTCGHSA enrichmentGHSA-p847-q8vx-c3fg · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Exploit-DBEDB-52668
    Published Sep 1, 2026

    miniOrange 5.4.3 - Unauthenticated Auth Bypass

    Open source ↗

Frequently asked(5)

What is CVE-2026-15013?
CVE-2026-15013 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-15013 published?
The CVE record for CVE-2026-15013 was published on July 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 7, 2026; the record at its source may have been updated since.
Is CVE-2026-15013 actively exploited?
CVE-2026-15013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15013?
CVE-2026-15013 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15013?
No fix for CVE-2026-15013 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists cyberlord92 SAML Single Sign On – SSO Login versions up to and including 5.4.3 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15013 are linked in the Vendor Advisories panel on this page.

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.