CVE 9.8 CRITICAL

OTP Login With Phone Number, OTP Verification <= 1.8.60 - Unauthenticated Authentication Bypass via Firebase OTP Verification_CVE-2026-3655

9.8 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

AI Analysis

Unauthenticated authentication bypass via Firebase OTP verification

Basic Information

ID CVE-2026-3655
Source Wordfence
Published May 29, 2026 at 06:43

Affected Product

Vendor glboy
Product OTP Login With Phone Number, OTP Verification
Version 1.8.50
Affected Versions glboy OTP Login With Phone Number, OTP Verification 1.8.50

CWE Classification

AI Assessment

AI Score 9.8 / 10
AI Severity Critical
Vendor glboy
Product OTP Login With Phone Number, OTP Verification
Version 1.8.50-1.8.60

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.