CVE-2026-15212

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM 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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.8Exploit: 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 | 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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
14th
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 12× in last 7d / 67× 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.

Showing the most recent 100 of 213 total refreshes for this CVE.

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

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 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.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15212?
CVE-2026-15212 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15212?
No fix for CVE-2026-15212 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-15212 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs