WooCommerce OTP Login with Phone Number, OTP Verification Plugin lwp_ajax_register improper authentication

Summaryinfo

A vulnerability, which was classified as critical, was found in WooCommerce OTP Login with Phone Number, OTP Verification Plugin up to 1.8.47 on WordPress. Affected is the function lwp_ajax_register. The manipulation of the argument empty results in improper authentication. This vulnerability is cataloged as CVE-2025-8342. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in WooCommerce OTP Login with Phone Number, OTP Verification Plugin up to 1.8.47 on WordPress. It has been classified as critical. Affected is the function lwp_ajax_register. The manipulation of the argument empty with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at wordfence.com. This vulnerability is traded as CVE-2025-8342. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/15/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-24963). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• E-Commerce Management Software

Name

• WooCommerce OTP Login with Phone Number, OTP Verification Plugin

Version

• 1.8.0
• 1.8.1
• 1.8.2
• 1.8.3
• 1.8.4
• 1.8.5
• 1.8.6
• 1.8.7
• 1.8.8
• 1.8.9
• 1.8.10
• 1.8.11
• 1.8.12
• 1.8.13
• 1.8.14
• 1.8.15
• 1.8.16
• 1.8.17
• 1.8.18
• 1.8.19
• 1.8.20
• 1.8.21
• 1.8.22
• 1.8.23
• 1.8.24
• 1.8.25
• 1.8.26
• 1.8.27
• 1.8.28
• 1.8.29
• 1.8.30
• 1.8.31
• 1.8.32
• 1.8.33
• 1.8.34
• 1.8.35
• 1.8.36
• 1.8.37
• 1.8.38
• 1.8.39
• 1.8.40
• 1.8.41
• 1.8.42
• 1.8.43
• 1.8.44
• 1.8.45
• 1.8.46
• 1.8.47

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion