Description
The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass in versions 1.8.50 through 1.8.60. This is due to the Firebase verification flow in the `lwp_ajax_register` AJAX handler not binding the Firebase session to the phone number supplied in the request. The `idehweb_lwp_activate_through_firebase()` function validates that a Firebase OTP session is legitimate, but the `phoneNumber` returned by Firebase is never compared against the victim's stored phone number. This makes it possible for unauthenticated attackers to authenticate as any user who has a phone number stored in user meta, including administrators, by verifying their own Firebase session and supplying the victim's phone number in the same request.
Published: 2026-05-29
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The plugin’s Firebase OTP validation routine fails to verify that the phone number submitted with the OTP matches the phone number stored for the target user account. This oversight allows an attacker, without prior authentication, to obtain a valid Firebase session and supply any victim’s phone number to register or log in. Once logged in, the attacker gains full access to the victim’s WordPress account, including administrator accounts, enabling arbitrary content modifications, file uploads, or site takeover. The weakness is classified as CWE-287 (Improper Authentication).

Affected Systems

WordPress sites that have installed the "OTP Login With Phone Number, OTP Verification" plugin by glboy, specifically versions 1.8.50 through 1.8.60. Users with any phone number registered in their WordPress profile are susceptible.

Risk and Exploitability

The vulnerability carries a CVSS score of 9.8, indicating critical severity. No EPSS data is available, and the issue is not currently listed in the CISA KEV catalog. The attack vector is remote, requiring only HTTP requests to the plugin’s AJAX endpoint and knowledge of a user’s phone number. Successful exploitation leads to complete account compromise, so the risk to affected sites is high and the exploitability is considered feasible for knowledgeable attackers who can acquire or guess phone numbers from publicly exposed profiles.

Generated by OpenCVE AI on May 29, 2026 at 08:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the "OTP Login With Phone Number, OTP Verification" plugin to the latest version (1.8.61 or newer) where the Firebase verification flow correctly matches phone numbers.
  • If an upgrade cannot be performed immediately, deactivate the plugin’s phone number login feature or block the AJAX endpoint to prevent unauthenticated access until a patch is applied.
  • As a temporary workaround, remove or obfuscate phone numbers from user meta for sensitive accounts or disable the OTP verification entirely until the plugin update is deployed.

Generated by OpenCVE AI on May 29, 2026 at 08:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 29 May 2026 16:00:00 +0000

Type Values Removed Values Added
First Time appeared Glboy
Glboy otp Login With Phone Number, Otp Verification
Wordpress
Wordpress wordpress
Vendors & Products Glboy
Glboy otp Login With Phone Number, Otp Verification
Wordpress
Wordpress wordpress

Fri, 29 May 2026 11:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 29 May 2026 07:45:00 +0000

Type Values Removed Values Added
Description The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass in versions 1.8.50 through 1.8.60. This is due to the Firebase verification flow in the `lwp_ajax_register` AJAX handler not binding the Firebase session to the phone number supplied in the request. The `idehweb_lwp_activate_through_firebase()` function validates that a Firebase OTP session is legitimate, but the `phoneNumber` returned by Firebase is never compared against the victim's stored phone number. This makes it possible for unauthenticated attackers to authenticate as any user who has a phone number stored in user meta, including administrators, by verifying their own Firebase session and supplying the victim's phone number in the same request.
Title OTP Login With Phone Number, OTP Verification <= 1.8.60 - Unauthenticated Authentication Bypass via Firebase OTP Verification
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Glboy Otp Login With Phone Number, Otp Verification
Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-05-29T10:05:49.537Z

Reserved: 2026-03-06T18:14:33.842Z

Link: CVE-2026-3655

cve-icon Vulnrichment

Updated: 2026-05-29T10:05:44.880Z

cve-icon NVD

Status : Deferred

Published: 2026-05-29T08:16:18.920

Modified: 2026-05-29T13:09:05.450

Link: CVE-2026-3655

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-29T15:47:29Z

Weaknesses