Vulnerability 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.
CVSS Score
CRITICAL
Related Weaknesses (CWE)
References
- https://plugins.trac.wordpress.org/browser/login-with-phone-number/tags/1.8.60/i
- https://plugins.trac.wordpress.org/browser/login-with-phone-number/tags/1.8.60/i
- https://plugins.trac.wordpress.org/browser/login-with-phone-number/tags/1.8.60/i
- https://plugins.trac.wordpress.org/browser/login-with-phone-number/trunk/inc/aja
- https://plugins.trac.wordpress.org/changeset/3479314/login-with-phone-number/tru
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7fc410f2-5f2b-4eea-a0f
FAQ
What is CVE-2026-3655?
CVE-2026-3655 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 `l...
How severe is CVE-2026-3655?
CVE-2026-3655 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-3655?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.