CVE-2026-115967

OTP Login With Phone Number, OTP Verification <= 1.8.78 - Authenticated (Subscriber+) Account Takeover

2026-10-27 00:00
Peter Tang

Strategic Overview

Status
Patched in 1.8.79
Affected Plugin
OTP Login With Phone Number, OTP Verification
Affected Version
<= 1.8.78
CVSS
8.8High
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-115967
View all OTP Login With Phone Number, OTP Verification vulnerabilities

At a glance

CVE-2026-115967 is a high-severity Improper Authentication vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.8.78. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.8.79; sites on affected versions should update now. Disclosed October 2026, reported by Peter Tang.

Vulnerability Overview

The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to Account Takeover in all versions up to, and including, 1.8.78. This is due to missing capability check in lwp_update_phonenumber_field() allowing any authenticated user to set or overwrite the phone_number user meta used as a login credential. This makes it possible for authenticated attackers, with subscriber-level access and above, to self-assign another user's registered phone number and authenticate as that user via OTP login.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-287: Improper Authentication

OTP Login With Phone Number, OTP Verification <= 1.8.78 carries this weakness at lwp_update_phonenumber_field(), and reaching it takes an account at Subscriber level or above. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For OTP Login With Phone Number, OTP Verification the fix is 1.8.79: builds <= 1.8.78 are affected, anything from 1.8.79 onward is not.

Remediation

Update to version 1.8.79, 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.79 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-115967https://www.wordfence.com/threat-intel/vulnerabilities/id/6b98996c-96b1-4794-8719-359b5c1ef8cehttps://nvd.nist.gov/vuln/detail/CVE-2026-115967

Related records

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