CVE-2026-65570

OTP Login With Phone Number, OTP Verification <= 1.8.70 - OTP Brute Force

2026-08-06 00:00
she11f

Strategic Overview

Status
Patched in 1.8.71
Affected Version
<= 1.8.70
CVSS
9.8Critical
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2026-65570
View all OTP Login With Phone Number, OTP Verification vulnerabilities

At a glance

CVE-2026-65570 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.8.70. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.8.71; sites on affected versions should update now. Disclosed August 2026, reported by she11f.

Vulnerability Overview

The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to OTP Brute Force in all versions up to, and including, 1.8.70. This makes it possible for unauthenticated attackers to brute force and bypass OTP verification.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

Reaching this weakness in OTP Login With Phone Number, OTP Verification <= 1.8.70 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For OTP Login With Phone Number, OTP Verification the fix is 1.8.71: builds <= 1.8.70 are affected, anything from 1.8.71 onward is not.

Remediation

Update to version 1.8.71, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: OTP Login With Phone Number, OTP Verification 1.8.71 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C