Home

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 Reserved 2026-03-06 | Published 2026-05-29 | Updated 2026-05-29 | Assigner Wordfence




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

Problem types

CWE-287 Improper Authentication

Product status

Default status
unaffected

1.8.50 (semver)
affected

Timeline

2026-03-06:Vendor Notified
2026-05-28:Disclosed

Credits

lucky_buddy finder

References

www.wordfence.com/...-5f2b-4eea-a0fb-fe58f988f95f?source=cve

plugins.trac.wordpress.org/...s/1.8.60/inc/ajax-handlers.php

plugins.trac.wordpress.org/...s/1.8.60/inc/ajax-handlers.php

plugins.trac.wordpress.org/...s/1.8.60/inc/ajax-handlers.php

plugins.trac.wordpress.org/...er/trunk/inc/ajax-handlers.php

plugins.trac.wordpress.org/...runk%2Finc%2Fajax-handlers.php

cve.org (CVE-2026-3655)

nvd.nist.gov (CVE-2026-3655)

Download JSON