CVE-2024-5150

Login with phone number <= 1.7.26 - Authentication Bypass due to Missing Empty Value Check

2024-05-28 00:00
István Márton

Strategic Overview

Status
Patched in 1.7.27
Affected Plugin
OTP Login With Phone Number, OTP Verification
Affected Version
<= 1.7.26
CVSS
9.8Critical
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2024-5150
View all OTP Login With Phone Number, OTP Verification vulnerabilities

At a glance

CVE-2024-5150 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.7.26. 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.7.27; sites on affected versions should update now. Disclosed May 2024, reported by István Márton.

Vulnerability Overview

The Login with phone number plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.7.26. This is due to the 'activation_code' default value is empty, and the not empty check is missing in the 'lwp_ajax_register' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user email. The vulnerability is patched in version 1.7.26, but there is an issue in the patch that causes the entire function to not work, and this issue is fixed in version 1.7.27.

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

OTP Login With Phone Number, OTP Verification <= 1.7.26 carries this weakness at activation_code, and reaching it 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.7.27: builds <= 1.7.26 are affected, anything from 1.7.27 onward is not.

Remediation

Update to version 1.7.27, 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.27 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-5150https://www.wordfence.com/threat-intel/vulnerabilities/id/cf34eb9f-f6e9-4a7a-8459-c86f9fa3dad8https://nvd.nist.gov/vuln/detail/CVE-2024-5150

Related records

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