WooCommerce OTP Login With Phone Number, OTP Verification <= 1.8.47 - Authentication Bypass
Strategic Overview
- Status
- Patched in 1.8.48
- Affected Plugin
- OTP Login With Phone Number, OTP Verification
- Affected Version
<= 1.8.47- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-8342
At a glance
CVE-2025-8342 is a high-severity Missing Authorization vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.8.47. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.8.48; sites on affected versions should update now. Disclosed August 2025, reported by Arkadiusz Hydzik.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in OTP Login With Phone Number, OTP Verification <= 1.8.47 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For OTP Login With Phone Number, OTP Verification the fix is 1.8.48: builds <= 1.8.47 are affected, anything from 1.8.48 onward is not.
Remediation
Update to version 1.8.48, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: OTP Login With Phone Number, OTP Verification 1.8.48 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in OTP Login With Phone Number, OTP Verification
- 9.8CVE-2026-65570: OTP Login With Phone Number OTP Brute Force
CVE-2026-65570 - 9.8CVE-2026-3655: OTP Login With Phone Number Authentication Bypass
CVE-2026-3655 - 9.8CVE-2024-5150: Login with phone number Authentication Bypass
CVE-2024-5150 - 8.8CVE-2024-6482: Login with phone number Authorization Bypass
CVE-2024-6482 - 8.8CVE-2024-32507: Login… Unauthorized Account Password Change
CVE-2024-32507 - 8.8CVE-2023-4916: Login with phone number CSRF to User Password Change
CVE-2023-4916 - 8.1CVE-2024-6125: Login with phone… Insecure Password Reset Mechanism
CVE-2024-6125 - 6.5CVE-2022-0593: Login with phone number <= 1.3.6 Remote Plugin Deletion
CVE-2022-0593
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C