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.
CVE-2026-12215
Score 5.3 from GitHub Security Advisory published 2026-09-11. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity53% × 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
References (7)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mobile-login-woocommerce/tags/2.7.2/includes/class-xoo-ml-geolocation.php#L24
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mobile-login-woocommerce/tags/2.7.2/includes/class-xoo-ml-otp-handler.php#L155
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mobile-login-woocommerce/tags/2.7.2/includes/class-xoo-ml-otp-handler.php#L24
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mobile-login-woocommerce/tags/2.7.2/includes/class-xoo-ml-verification.php#L472
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mobile-login-woocommerce/tags/2.7.2/includes/class-xoo-ml-verification.php#L84
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3639216%40mobile-login-woocommerce%2Ftrunk%2Fincludes%2Fclass-xoo-ml-otp-handler.php&old=3419316%40mobile-login-woocommerce%2Ftrunk%2Fincludes%2Fclass-xoo-ml-otp-handler.php&sfp_email=&sfph_mail=
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/4bd4b379-6d7d-4cfe-bb16-a931c5d68d02?source=cve
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.
- 2026-09-21 10:23 UTCEG score recompute
- 2026-09-21 10:23 UTCGHSA enrichment
- 2026-09-20 20:15 UTCEPSS rescore
- 2026-09-20 08:11 UTCEG score recompute
- 2026-09-20 08:11 UTCGHSA enrichment
- 2026-09-19 05:58 UTCEG score recompute
- 2026-09-19 05:58 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 03:46 UTCEG score recompute
- 2026-09-18 03:46 UTCGHSA enrichment
- 2026-09-17 01:34 UTCEG score recompute
- 2026-09-17 01:34 UTCGHSA enrichment
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-15 23:22 UTCEG score recompute
- 2026-09-15 23:22 UTCGHSA enrichment
- 2026-09-14 21:10 UTCGHSA enrichment
- 2026-09-13 18:53 UTCEG score recompute
- 2026-09-13 18:52 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 16:36 UTCEG score recompute
- 2026-09-12 16:36 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 14:23 UTCEG score recompute
- 2026-09-11 14:23 UTCGHSA enrichment
Show 7 moreShow fewer
- 2026-09-11 13:50 UTCEG score recompute
- 2026-09-11 13:50 UTCGHSA enrichment
- 2026-09-11 13:32 UTCEG score recompute
- 2026-09-11 13:32 UTCGHSA enrichment
- 2026-09-11 04:20 UTCEG score recompute
- 2026-09-11 03:50 UTCEG score recompute
- 2026-09-11 03:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-434
Frequently asked(5)
What is CVE-2026-12215?
When was CVE-2026-12215 disclosed?
Is CVE-2026-12215 actively exploited?
What is the CVSS score of CVE-2026-12215?
How do I remediate CVE-2026-12215?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12215
Is Your Infrastructure Affected by CVE-2026-12215?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.