Login with phone number <= 1.7.49 - Authenticated (Subscriber+) Authorization Bypass to Privilege Escalation
Strategic Overview
- Status
- Patched in 1.7.50
- Affected Plugin
- OTP Login With Phone Number, OTP Verification
- Affected Version
<= 1.7.49- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2024-6482
At a glance
CVE-2024-6482 is a high-severity Improper Privilege Management vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.7.49. 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.7.50; sites on affected versions should update now. Disclosed September 2024, reported by Thanh Nam Tran.
Vulnerability Overview
The Login with phone number plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.7.49. This is due to a lack of validation and missing capability check on user-supplied data in the 'lwp_update_password_action' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update their role to any other role, including Administrator. The vulnerability was partially patched in version 1.7.40. The login with phone number pro plugin was required to exploit the vulnerability in versions 1.7.40 - 1.7.49.
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-269: Improper Privilege Management
OTP Login With Phone Number, OTP Verification <= 1.7.49 carries this weakness at lwp_update_password_action, and reaching it takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For OTP Login With Phone Number, OTP Verification the fix is 1.7.50: builds <= 1.7.49 are affected, anything from 1.7.50 onward is not.
Remediation
Update to version 1.7.50, 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.50 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in OTP Login With Phone Number, OTP Verification
- 9.8CVE-2026-65570: OTP Login With Phone Number OTP Brute Force
CVE-2026-65570 - 9.8CVE-2026-3655: OTP Login With Phone Number Authentication Bypass
CVE-2026-3655 - 9.8CVE-2024-5150: Login with phone number Authentication Bypass
CVE-2024-5150 - 8.8CVE-2024-32507: Login… Unauthorized Account Password Change
CVE-2024-32507 - 8.8CVE-2023-4916: Login with phone number CSRF to User Password Change
CVE-2023-4916 - 8.1CVE-2025-8342: WooCommerce OTP Login… Authentication Bypass
CVE-2025-8342 - 8.1CVE-2024-6125: Login with phone… Insecure Password Reset Mechanism
CVE-2024-6125 - 6.5CVE-2022-0593: Login with phone number <= 1.3.6 Remote Plugin Deletion
CVE-2022-0593
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C