{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8342 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8342 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8342 is a high-severity authentication bypass vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 15 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8342 and fix it if it is affected.\n\nWhat it is: CVE-2025-8342 is a high-severity authentication bypass vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 15 Aug 2025. 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-2025-8342 in the wild and no public exploit code.\n\nAffected product: glboy OTP Login With Phone Number, OTP Verification. 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-2025-8342/ (Markdown: https://insights.sbomify.com/CVE-2025-8342/index.md)","id":"CVE-2025-8342","markdown":"https://insights.sbomify.com/CVE-2025-8342/index.md","name":"CVE-2025-8342","record":{"aliases":["GHSA-8cmp-8cwc-qcv3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass OTP verification to gain administrative access to user accounts if the Firebase API key is not configured.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The WooCommerce OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass due to insufficient empty value checking in the lwp_ajax_register function in all versions up to, and including, 1.8.47. This makes it possible for unauthenticated attackers to bypass OTP verification and gain administrative access to any user account with a configured phone number by exploiting improper Firebase API error handling when the Firebase API key is not configured.","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":"WooCommerce OTP Login With Phone Number, OTP Verification \u003c= 1.8.47 - Authentication Bypass","id":"CVE-2025-8342","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"openviglet shio ShStaticFileAPI.java shStaticFilePreUpload path traversal","id":"CVE-2025-8343"},"packages":[],"prev":{"headline":"SSRF in Infinity Datasource Plugin","id":"CVE-2025-8341"},"products":["OTP Login With Phone Number, OTP Verification"],"published":"2025-08-15","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["glboy"]},"summary":"Unauthenticated attackers can bypass OTP verification to gain administrative access to user accounts if the Firebase API key is not configured.","url":"https://insights.sbomify.com/CVE-2025-8342/"}