Security incident · CVE-2026-3655
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.
Published May 29, 2026 · catalog updated Jul 21, 2026 · The OTP Login With
Check if you run it
No confirmed exploitation is on record for CVE-2026-3655. EPSS is 0.90%. Act only if a listed version of The OTP Login With is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (The OTP Login With).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Critical9.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.90%
- Remediation
- Not established
- Affected products
- See sources for product scope
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 AJAX handler not binding the Firebase session to the phone number supplied in the request. The function validates that a Firebase OTP session is legitimate, but the 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.
No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.
How to fix CVE-2026-3655
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-3655. EPSS is 0.90%. Act only if a listed version of The OTP Login With is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-287: Improper Authentication. EPSS 0.90%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 29, 2026 · NIST NVD
Detected
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 AJAX handler not binding the Firebase session to the phone number supplied in the request. The function validates that a Firebase OTP session is legitimate, but the returned by Firebase is never compare
Jul 21, 2026 · NIST NVD
Updated
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 AJAX handler not binding the Firebase session to the phone number supplied in the request. The function validates that a Firebase OTP session is legitimate, but the returned by Firebase is never compare
Sources
- CVE.orgVulnerability recordCVE-2026-3655
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-3655
30-day exploitation probability 0.9%
first.org - NIST NVDVulnerability recordCVE-2026-3655
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 AJAX handler not binding the Firebase session to the phone num
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.