CVE-2026-15210: OTP Login With Phone Number, OTP Verification (WordPress plugin) · Improper Authentication
Affects OTP Login With Phone Number, OTP Verification (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.8.71 as a priority.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.71
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade OTP Login With Phone Number, OTP Verification (WordPress plugin) to 1.8.71.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OTP Login With Phone Number, OTP Verification | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to the OTP verification endpoint if possible and monitor for suspicious OTP request activity. Implement rate limiting or other controls to mitigate brute-force attempts if feasible.
Description
The OTP Login With Phone Number, OTP Verification WordPress plugin before version 1.8.71 has an improper authentication vulnerability. It does not limit the number of OTP verification attempts nor invalidate the OTP after incorrect guesses. This allows unauthenticated attackers to brute-force short numeric OTP codes and potentially take over any user account, including administrators.