WordPress security changelog
CRITICAL CVE-2026-3655 Deferred

OTP Login With Phone Number, OTP Verification: Privilege escalation or authentication bypass

OTP Login With Phone Number, OTP Verification is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess. The published affected range is 1.8.50 through 1.8.60.

CVE / CNA score 9.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
OTP Login With Phone Number, OTP Verification
Plugin slug
login-with-phone-number
Affected
1.8.50 through 1.8.60
Safe version
> 1.8.60
Published
May 29, 2026
Weakness
CWE-287 — Improper Authentication

This CVE was published May 29, 2026 and is one of 14 known issues for this plugin.

What to do

Update, patch or deactivate.

Update OTP Login With Phone Number, OTP Verification to a release after 1.8.60, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical 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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

Primary and upstream sources