CVE-2026-75807

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-29. A secondary CVSS source baseline 7.5; 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 week
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed 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.6 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 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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

August 29, 2026

Last Modified

August 31, 2026

References (5)

Vendor Advisories for CVE-2026-75807(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 20× in last 7d / 104× 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 168 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 68 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-75807?
CVE-2026-75807 is a high-severity vulnerability; its CVE record was published on August 29, 2026. 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 mosamlloginvalidate() ACS handler persisting the X.509 certificate extracted from an incoming SAMLResponse into the mosamlrequiredcertificate…
When was the CVE record for CVE-2026-75807 published?
The CVE record for CVE-2026-75807 was published on August 29, 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 31, 2026; the record at its source may have been updated since.
Is CVE-2026-75807 actively exploited?
CVE-2026-75807 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75807?
CVE-2026-75807 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75807?
No fix for CVE-2026-75807 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.6 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-75807 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-75807?

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

Book a Demo →Browse All CVEs