CVE-2026-15212

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

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

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

The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option 'enable_nonce_check', which is absent from the default 'wpo365_options' array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied 'settings' payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to 'administrator' — via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 24, 2026

References (3)

Vendor Advisories for CVE-2026-15212(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 30× in last 7d / 33× 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-08-01 17:43 UTCGHSA enrichment
  2. 2026-08-01 06:26 UTCEG score recompute
  3. 2026-08-01 06:26 UTCGHSA enrichment
  4. 2026-08-01 04:15 UTCEPSS rescore
  5. 2026-07-31 19:05 UTCGHSA enrichment
  6. 2026-07-31 07:49 UTCGHSA enrichment
  7. 2026-07-30 20:32 UTCEG score recompute
  8. 2026-07-30 20:32 UTCGHSA enrichment
  9. 2026-07-30 16:27 UTCEPSS rescore
  10. 2026-07-30 08:56 UTCEG score recompute
  11. 2026-07-30 08:56 UTCGHSA enrichment
  12. 2026-07-30 01:30 UTCEPSS rescore
  13. 2026-07-29 21:39 UTCGHSA enrichment
  14. 2026-07-29 10:22 UTCGHSA enrichment
  15. 2026-07-28 23:04 UTCEG score recompute
  16. 2026-07-28 23:04 UTCGHSA enrichment
  17. 2026-07-28 15:36 UTCEPSS rescore
  18. 2026-07-28 11:36 UTCGHSA enrichment
  19. 2026-07-28 00:18 UTCEG score recompute
  20. 2026-07-28 00:18 UTCGHSA enrichment
  21. 2026-07-27 14:13 UTCEPSS rescore
  22. 2026-07-27 12:59 UTCGHSA enrichment
  23. 2026-07-27 01:42 UTCEG score recompute
  24. 2026-07-27 01:41 UTCGHSA enrichment
  25. 2026-07-26 14:54 UTCEPSS rescore
Show 8 more
  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:24 UTCEG score recompute
  3. 2026-07-26 14:24 UTCGHSA enrichment
  4. 2026-07-26 03:07 UTCEG score recompute
  5. 2026-07-26 03:07 UTCGHSA enrichment
  6. 2026-07-24 14:17 UTCEPSS rescore
  7. 2026-07-23 19:52 UTCEG score recompute
  8. 2026-07-23 19:51 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15212?
CVE-2026-15212 is a high vulnerability published on July 23, 2026. The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the AjaxService::verifyajaxrequest() helper gating its wpverifynonce() call behind the boolean option 'enablenoncecheck', which is absent from the default…
When was CVE-2026-15212 disclosed?
CVE-2026-15212 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15212 actively exploited?
CVE-2026-15212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-15212?
CVE-2026-15212 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-15212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15212, 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-15212

Explore →

Is Your Infrastructure Affected by CVE-2026-15212?

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

Start Free Scan →Browse All CVEs