Radar sectionsDatabase
Check my site
WordPress plugin

WooCommerce OTP Login With Phone Number, OTP Verification <= 1.8.47 — Authentication Bypass

CVE-2025-8342Published · Updated

Action summary

Affected: ≤1.8.47Update to 1.8.48 or newer

All remediation steps
Severity
High8.1
CVSS
8.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:H Attack complexity
High
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-862 Missing Authorization
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

OTP Login With Phone Number, OTP Verification login-with-phone-number

  1. Affected≤ 1.8.47
  2. Patched in1.8.48

Update to 1.8.48 or newer.

You are affected if you run ≤ 1.8.47. Version 1.8.48 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under OTP Login With Phone Number, OTP Verification.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.8.48, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch OTP Login With Phone Number, OTP Verification to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Arkadiusz Hydzik.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in OTP Login With Phone Number, OTP Verification

All 18
More vulnerabilities in OTP Login With Phone Number, OTP Verification
SeverityVulnerabilityCVEPublished
High8.8Authenticated (Subscriber+) Account Takeover
≤1.8.78Update to 1.8.79
CVE-2026-115967
High7.3Unauthenticated Privilege Escalation
≤1.8.77Update to 1.8.78
CVE-2026-110373
Medium4.3Missing Authorization
≤1.8.77Update to 1.8.78
CVE-2026-110374
Critical9.8OTP Brute Force
≤1.8.70Update to 1.8.71
CVE-2026-65570
Critical9.8Unauthenticated Authentication Bypass via Firebase OTP Verification
1.8.50 – 1.8.60Update to 1.8.61
CVE-2026-3655

Same weakness (Missing Authorization)

All Missing Authorization
Other Missing Authorization vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 8.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?