{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12215 is a medium-severity authentication bypass vulnerability in xootix OTP Login \u0026 Register Woocommerce, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12215 and fix it if it is affected.\n\nWhat it is: CVE-2026-12215 is a medium-severity authentication bypass vulnerability in xootix OTP Login \u0026 Register Woocommerce, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12215 in the wild and no public exploit code.\n\nAffected product: xootix OTP Login \u0026 Register Woocommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12215/ (Markdown: https://insights.sbomify.com/CVE-2026-12215/index.md)","id":"CVE-2026-12215","markdown":"https://insights.sbomify.com/CVE-2026-12215/index.md","name":"CVE-2026-12215","record":{"aliases":["GHSA-26m4-chch-cqh3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can brute-force weak OTPs to bypass authentication and gain administrator access in the OTP Login \u0026 Register Woocommerce plugin.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"The OTP Login \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"OTP Login \u0026 Register Woocommerce \u003c= 2.7.2 - Unauthenticated Authentication Bypass via Brute Force","id":"CVE-2026-12215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"svaarala duktape duk_api_bytecode.c memory corruption","id":"CVE-2026-12216"},"packages":[],"prev":{"headline":"Qihoo 360 Total Security Nucleus Engine Monitoring Logic RpcStringBindingComposeW protection mechanism","id":"CVE-2026-12214"},"products":["OTP Login \u0026 Register Woocommerce"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-11","vendors":["xootix"]},"summary":"Unauthenticated attackers can brute-force weak OTPs to bypass authentication and gain administrator access in the OTP Login \u0026 Register Woocommerce plugin.","url":"https://insights.sbomify.com/CVE-2026-12215/"}