CVE-2024-32507

Login with phone number <= 1.7.16 - Unauthorized Account Password Change to Privilege Escalation

2024-04-15 00:00
Emili Castells

Strategic Overview

Status
Patched in 1.7.17
Affected Plugin
OTP Login With Phone Number, OTP Verification
Affected Version
<= 1.7.16
CVSS
8.8High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-32507
View all OTP Login With Phone Number, OTP Verification vulnerabilities

At a glance

CVE-2024-32507 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.7.16. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.7.17; sites on affected versions should update now. Disclosed April 2024, reported by Emili Castells.

Vulnerability Overview

The Login with phone number plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.7.16. This is due to the plugin not properly verifying the identity of a user who is trying to reset a password. This makes it possible for authenticated attackers, with subscriber-level access and above, to gain access to administrative user accounts.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in OTP Login With Phone Number, OTP Verification <= 1.7.16 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For OTP Login With Phone Number, OTP Verification the fix is 1.7.17: builds <= 1.7.16 are affected, anything from 1.7.17 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-32507https://www.wordfence.com/threat-intel/vulnerabilities/id/95247ff5-0277-4270-a1ea-221ea2ecee0chttps://nvd.nist.gov/vuln/detail/CVE-2024-32507

Related records

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