Skip to content

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

CriticalCVSS 9.8 EPSS 0.51%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: total
Technology
WordPress

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.

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
glboy OTP Login With Phone Number, OTP Verification >= 1.8.50, <= 1.8.60 after 1.8.60 Fixed
wordpress login-with-phone-number(WordPress) >= 1.8.50, < 1.8.61 1.8.61 Fixed

Affected products

ProductAffected versionsFixed in
glboy OTP Login With Phone Number, OTP Verification >= 1.8.50, <= 1.8.60 No fix listed
wordpress login-with-phone-number(WordPress) >= 1.8.50, < 1.8.61 1.8.61

References