Authentication Bypass in OTP Login With Phone Number, OTP Verification (WordPress plugin) (CVE-2026-3655)
Summary
Authentication bypass in OTP Login With Phone Number, OTP Verification (WordPress plugin) (CVE-2026-3655). Successful exploitation can lead to full system takeover. Exploitable via lwp_ajax_register.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3655 has been found in OTP Login With Phone Number, OTP Verification (WordPress plugin).
Attackers can target a specific entry point like lwp_ajax_register over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OTP Login With Phone Number, OTP Verification (WordPress plugin) CVE-2026-3655" on the vendor's site.
CVE-2026-3655 (OTP Login With Phone Number, OTP Verification (WordPress plugin)) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: lwp_ajax_register / phoneNumber
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in OTP Login With Phone Number, OTP Verification (WordPress plugin). Attackers reach the vulnerable code path via lwp_ajax_register without authentication.
Check the vendor advisory for the affected versions of OTP Login With Phone Number, OTP Verification (WordPress plugin). Attack surface: lwp_ajax_register / phoneNumber.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OTP Login With Phone Number, OTP Verification (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web nvd.nist.gov
- web github.com