CVE-2026-12215

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-11. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

The OTP Login & Register Woocommerce plugin for WordPress is vulnerable to Authentication Bypass via OTP Brute Force in all versions up to, and including, 2.7.2. The vulnerability exists because the OTP rate-limit attempt counter in process_otp_form is keyed exclusively on the attacker-controlled xoo_ml_user_ip_data cookie's ip_address field, allowing unlimited counter resets by simply rotating the cookie, while the OTP itself is generated with PHP's non-cryptographic rand() function over a default space of only 9,000 possible values (1000–9999), and both the OTP issuance endpoint (xoo_ml_login_with_otp) and verification endpoint (xoo_ml_otp_form_submit) are registered as unauthenticated wp_ajax_nopriv actions with no nonce or capability checks. This makes it possible for unauthenticated attackers to brute-force the OTP for any registered account and obtain a full WordPress authentication session — including for administrator accounts — via wp_set_auth_cookie() in login_user_with_otp(). Exploitation requires the attacker to know the target user's registered phone number, which is used to trigger OTP issuance via the unauthenticated xoo_ml_login_with_otp endpoint.

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

Published

September 11, 2026

Last Modified

September 11, 2026

Vendor Advisories for CVE-2026-12215(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 16× in last 7d / 32× 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-09-21 10:23 UTCEG score recompute
  2. 2026-09-21 10:23 UTCGHSA enrichment
  3. 2026-09-20 20:15 UTCEPSS rescore
  4. 2026-09-20 08:11 UTCEG score recompute
  5. 2026-09-20 08:11 UTCGHSA enrichment
  6. 2026-09-19 05:58 UTCEG score recompute
  7. 2026-09-19 05:58 UTCGHSA enrichment
  8. 2026-09-18 19:27 UTCEPSS rescore
  9. 2026-09-18 03:46 UTCEG score recompute
  10. 2026-09-18 03:46 UTCGHSA enrichment
  11. 2026-09-17 01:34 UTCEG score recompute
  12. 2026-09-17 01:34 UTCGHSA enrichment
  13. 2026-09-16 05:14 UTCEPSS rescore
  14. 2026-09-15 23:22 UTCEG score recompute
  15. 2026-09-15 23:22 UTCGHSA enrichment
  16. 2026-09-14 21:10 UTCGHSA enrichment
  17. 2026-09-13 18:53 UTCEG score recompute
  18. 2026-09-13 18:52 UTCGHSA enrichment
  19. 2026-09-13 16:46 UTCEPSS rescore
  20. 2026-09-12 16:36 UTCEG score recompute
  21. 2026-09-12 16:36 UTCGHSA enrichment
  22. 2026-09-12 15:00 UTCEPSS rescore
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-11 14:23 UTCEG score recompute
  25. 2026-09-11 14:23 UTCGHSA enrichment
Show 7 more
  1. 2026-09-11 13:50 UTCEG score recompute
  2. 2026-09-11 13:50 UTCGHSA enrichment
  3. 2026-09-11 13:32 UTCEG score recompute
  4. 2026-09-11 13:32 UTCGHSA enrichment
  5. 2026-09-11 04:20 UTCEG score recompute
  6. 2026-09-11 03:50 UTCEG score recompute
  7. 2026-09-11 03:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-12215?
CVE-2026-12215 is a medium vulnerability published on September 11, 2026. The OTP Login & Register Woocommerce plugin for WordPress is vulnerable to Authentication Bypass via OTP Brute Force in all versions up to, and including, 2.7.2. The vulnerability exists because the OTP rate-limit attempt counter in processotpform is keyed exclusively on the attacker-controlled…
When was CVE-2026-12215 disclosed?
CVE-2026-12215 was first published in the National Vulnerability Database on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12215 actively exploited?
CVE-2026-12215 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 74.7% of all scored CVEs.
What is the CVSS score of CVE-2026-12215?
CVE-2026-12215 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-12215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12215, 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-12215

Explore →

Is Your Infrastructure Affected by CVE-2026-12215?

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