Description
The OTP Login With Phone Number, OTP Verification WordPress plugin before 1.8.71 does not limit the number of OTP verification attempts or invalidate a one-time login code after a wrong guess, and an unauthenticated user can request a login code for any account. Because the code is a short numeric OTP, an attacker can brute-force it and take over any account, including an administrator's.
Published: 2026-08-05
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an unauthenticated attacker to request a one-time password (OTP) for any user account via the OTP Login With Phone Number, OTP Verification plugin. Because the plugin does not enforce any rate limiting or invalidate the OTP after a failed guess, a brute‑force attack on the short numeric code can succeed within a reasonable number of attempts, permitting the attacker to authenticate as the target, including administrators. This represents an authentication bypass that can compromise confidentiality, integrity, and availability of the site and its users.

Affected Systems

WordPress sites that have the OTP Login With Phone Number, OTP Verification plugin installed prior to version 1.8.71. All user accounts exposed through this plugin are vulnerable, regardless of role. The issue affects any WordPress instance that has not applied the security patch included in 1.8.71 or later.

Risk and Exploitability

The attack can be performed from any location with internet connectivity to the targeted WordPress site, making it a remote unauthenticated vector. Since the OWASP Common Weakness enumeration points to missing rate limiting, an attacker can iterate guesses quickly without detection. Exploitability is high because no special privileges or additional configuration are required. No official KEV listing or EPSS data is available, but the lack of protective controls makes this a critical asset risk.

Generated by OpenCVE AI on August 5, 2026 at 07:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the OTP Login With Phone Number, OTP Verification plugin to version 1.8.71 or newer, which implements OTP invalidation and rate limiting.
  • If the patch cannot be applied immediately, implement an external rate‑limiting or CAPTCHA on the OTP request endpoint to reduce brute‑force attempts.
  • Disable or temporarily remove the OTP login feature if it is not essential to your authentication flow.
  • Consider extending the OTP length or using alphanumeric codes to increase brute‑force difficulty.
  • Enable monitoring of OTP request and login attempt logs to detect anomalous activity.

Generated by OpenCVE AI on August 5, 2026 at 07:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-307

Wed, 05 Aug 2026 06:30:00 +0000

Type Values Removed Values Added
Description The OTP Login With Phone Number, OTP Verification WordPress plugin before 1.8.71 does not limit the number of OTP verification attempts or invalidate a one-time login code after a wrong guess, and an unauthenticated user can request a login code for any account. Because the code is a short numeric OTP, an attacker can brute-force it and take over any account, including an administrator's.
Title Login/Signup with Phone Number, OTP Verification < 1.8.71 - Unauthenticated Account Takeover via OTP Brute Force
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-05T06:00:12.055Z

Reserved: 2026-07-09T07:35:39.136Z

Link: CVE-2026-15210

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T07:30:16Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-307

    Improper Restriction of Excessive Authentication Attempts