External risk intelligence

OTP Login With Phone Number WordPress Plugin Account Takeover via Brute-Force

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-15210

The vulnerability affects a WordPress plugin designed to provide authentication and login functionality via OTP. Such plugins are deployed directly on the public-facing web interface of a site to allow user access and are intended to be reachable by external users for standard account login operations.

Authentication Bypass

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical security vulnerability in a WordPress plugin that handles login verification. The flaw allows unauthenticated attackers to repeatedly guess one-time login codes, potentially leading to unauthorized account takeovers, including administrative accounts.

  • Unprotected login attempts allow account takeover.
  • Executive attention ensures relevant systems are checked.
  • Confirm if this plugin is used and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can initiate an attack by sending an OTP login request for any user account on a vulnerable WordPress site. Because the system does not limit verification attempts or invalidate codes after incorrect guesses, the attacker can repeatedly guess the short numeric OTP. This brute-force approach allows them to bypass authentication and gain control of any account, including administrative ones.

  • Unauthenticated network access required.
  • Brute-force OTP verification attempts.
  • Account takeover, including administrator.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in an OTP login plugin could allow an unauthenticated attacker to gain unauthorized access to any user account, including administrator accounts, by repeatedly guessing one-time login codes. The weakness lies in the plugin's failure to limit verification attempts or invalidate codes after incorrect guesses.

  • Any user account could be compromised.
  • Attacker brute-forces guessed OTP codes.
  • Unauthorized account access and control.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects the OTP Login With Phone Number, OTP Verification WordPress plugin. Website owners and their associated application or platform teams are likely responsible for addressing this issue. The first practical step involves identifying all instances of this plugin across your WordPress deployments, assessing their exposure to unauthenticated access, and confirming the business criticality of affected accounts. Once identified, engage the accountable owner to plan remediation.

  • Application owners should manage the issue.
  • Verify public-facing site exposure first.
  • Plan maintenance for remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the OTP Login With Phone Number WordPress plugin?

This plugin is a tool for WordPress sites that replaces or augments traditional password-based logins with a one-time passcode (OTP) sent via SMS or messaging. It is specifically designed to handle user authentication workflows by verifying phone numbers before granting access to a site's member or administrative areas.

What does CWE-287 mean for CVE-2026-15210?

CWE-287 refers to Improper Authentication. In the context of this vulnerability, it means the plugin fails to properly verify the identity of someone trying to log in. Because the system does not track or block incorrect guesses, it allows an unauthorized user to bypass the intended security check and gain entry to accounts without knowing the actual, valid secret code.

How does an attacker trigger this vulnerability?

An attacker initiates the process by requesting a login code for any target account. The flaw is triggered by the lack of rate-limiting or code invalidation after failed attempts. Simply clicking 'forgot password' or normal site activity does not trigger the bug; the vulnerability is specifically exploited through a sustained, automated series of incorrect code guesses against the authentication endpoint.

Is my site at risk if the login page is internal-only?

Halo Surface Signal indicates this plugin is intended for public-facing web interfaces to allow standard user logins. If your WordPress site is strictly restricted to an internal network with no path for external visitors to reach the login page, the likelihood of this specific attack is reduced, though it remains a security concern for any environment where the plugin is active and reachable.

How should I respond to this vulnerability?

The most effective first step is to audit your WordPress installations to locate any instances of the OTP Login With Phone Number, OTP Verification plugin. Once you confirm the plugin is in use, verify the version number and prioritize updating to version 1.8.71 or higher. If an update is not immediately feasible, consider temporarily disabling the plugin to prevent unauthorized account access.

References