CVE-2024-6125

Login with phone number <= 1.7.34 - Insecure Password Reset Mechanism

2024-06-18 00:00
István Márton

Strategic Overview

Status
Patched in 1.7.35
Affected Plugin
OTP Login With Phone Number, OTP Verification
Affected Version
<= 1.7.34
CVSS
8.1High
Weakness type
CWE-640 · Weak Password Recovery Mechanism for Forgotten Password
CVE
CVE-2024-6125
View all OTP Login With Phone Number, OTP Verification vulnerabilities

At a glance

CVE-2024-6125 is a high-severity Weak Password Recovery Mechanism for Forgotten Password vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.7.34. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7.35; sites on affected versions should update now. Disclosed June 2024, reported by István Márton.

Vulnerability Overview

The Login with phone number plugin for WordPress is vulnerable to unauthorized password resets in versions up to, and including 1.7.34. This is due to the plugin generating too weak a reset code, and the code used to reset the password has no attempt or time limit. This makes it possible for unauthenticated attackers to reset the password of arbitrary users by guessing a 6-digit numeric reset code.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, 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-640: Weak Password Recovery Mechanism for Forgotten Password

Reaching this weakness in OTP Login With Phone Number, OTP Verification <= 1.7.34 takes a caller who can reach the endpoint. A weak password recovery mechanism means the path that lets someone back into an account without their password is easier to complete than the password itself.

An attacker takes over an account through the recovery flow without ever seeing the password, and on an administrator account that is full control of the site. For OTP Login With Phone Number, OTP Verification the fix is 1.7.35: builds <= 1.7.34 are affected, anything from 1.7.35 onward is not.

Remediation

Update to version 1.7.35, 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.35 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-6125https://www.wordfence.com/threat-intel/vulnerabilities/id/301a67a5-226c-413a-9198-66747d1b1fd3https://nvd.nist.gov/vuln/detail/CVE-2024-6125

Related records

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