CVE-2026-3655 Auth bypass in OTP Login With Phone Number, OTP Verification
Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by exploiting a flaw in the Firebase OTP verification flow.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-3655?
CVE-2026-3655 is a critical authentication bypass vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2026-3655?
How do I fix CVE-2026-3655?
No fix has been published for CVE-2026-3655 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-3655 being exploited?
There is no known exploitation of CVE-2026-3655 in the wild and no public exploit code.
Sources
Also known as GHSA-8p28-978j-q34v.