CVE-2026-104759

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-10. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
8.1EG
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.5%CVSS: 8.1Exploit: 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 WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Authentication Bypass via OIDC Nonce Replay in all versions up to, and including, 44.1 This is due to Id_Token_Service_Deprecated::process_openidconnect_token() using the incompatible WordPress core wp_verify_nonce() function to validate a nonce produced by Nonce_Service::create_nonce() — a 64-character hex value that wp_verify_nonce() can never successfully verify — causing the nonce check to silently fail without terminating authentication, so execution continues into authenticate_oidc_user() with the attacker-supplied id_token. This makes it possible for unauthenticated attackers who have obtained a previously-issued, valid id_token for a target account to replay that token and authenticate as any WordPress user, including administrators, resulting in full site takeover. This vulnerability is only exploitable when the use_id_token_parser_v2 plugin option is enabled, as this is the configuration that routes token processing through the deprecated parser containing the broken nonce check.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.5% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 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 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

October 10, 2026

Last Modified

October 11, 2026

References (7)

Vendor Advisories for CVE-2026-104759(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 15× in last 7d / 15× 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.

  1. 2026-10-11 20:15 UTCEG score recompute
  2. 2026-10-11 17:32 UTCEG score recompute
  3. 2026-10-11 17:32 UTCGHSA enrichmentGHSA-p38j-g4g4-fm3g · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-11 17:01 UTCEG score recompute
  5. 2026-10-11 17:01 UTCGHSA enrichmentGHSA-p38j-g4g4-fm3g · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-10-11 15:01 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-10-11 07:34 UTCEG score recompute
  9. 2026-10-11 07:34 UTCGHSA enrichmentGHSA-p38j-g4g4-fm3g · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-10 19:59 UTCEG score recompute
  12. 2026-10-10 19:59 UTCGHSA enrichmentGHSA-p38j-g4g4-fm3g · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-10 08:22 UTCEG score recompute
  14. 2026-10-10 07:51 UTCEG score recomputeFirst assessed: 8.1 HIGH
  15. 2026-10-10 07:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104759?
CVE-2026-104759 is a high-severity vulnerability; its CVE record was published on October 10, 2026. The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Authentication Bypass via OIDC Nonce Replay in all versions up to, and including, 44.1 This is due to IdTokenServiceDeprecated::processopenidconnecttoken() using the incompatible WordPress…
When was the CVE record for CVE-2026-104759 published?
The CVE record for CVE-2026-104759 was published on October 10, 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 October 11, 2026; the record at its source may have been updated since.
Is CVE-2026-104759 actively exploited?
CVE-2026-104759 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104759?
CVE-2026-104759 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104759?
No fix for CVE-2026-104759 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 vendor advisories EchelonGraph has for CVE-2026-104759 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-104759?

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

Book a Demo →Browse All CVEs