Login with phone number <= 1.7.26 — Authentication Bypass due to Missing Empty Value Check
CVE-2024-5150Published · Updated Action summary
Affected: ≤1.7.26Update to 1.7.27 or newer
All remediation steps- Severity
- Critical9.8
- CVSS
- 9.8CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
OTP Login With Phone Number, OTP Verification login-with-phone-number
- Affected≤ 1.7.26
- Patched in1.7.27
Update to 1.7.27 or newer.
You are affected if you run ≤ 1.7.26. Version 1.7.27 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under OTP Login With Phone Number, OTP Verification.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 1.7.27, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch OTP Login With Phone Number, OTP Verification to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to István Márton.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in OTP Login With Phone Number, OTP Verification
All 18| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Authenticated (Subscriber+) Account Takeover ≤1.8.78Update to 1.8.79 | CVE-2026-115967 | |
| High7.3 | Unauthenticated Privilege Escalation ≤1.8.77Update to 1.8.78 | CVE-2026-110373 | |
| Medium4.3 | Missing Authorization ≤1.8.77Update to 1.8.78 | CVE-2026-110374 | |
| Critical9.8 | OTP Brute Force ≤1.8.70Update to 1.8.71 | CVE-2026-65570 | |
| Critical9.8 | Unauthenticated Authentication Bypass via Firebase OTP Verification 1.8.50 – 1.8.60Update to 1.8.61 | CVE-2026-3655 |
- High8.8Authenticated (Subscriber+) Account Takeover
≤1.8.78Update to 1.8.79
- High7.3Unauthenticated Privilege Escalation
≤1.8.77Update to 1.8.78
- Medium4.3Missing Authorization
≤1.8.77Update to 1.8.78
- Critical9.8OTP Brute Force
≤1.8.70Update to 1.8.71
- Critical9.8Unauthenticated Authentication Bypass via Firebase OTP Verification
1.8.50 – 1.8.60Update to 1.8.61
Timeline
CVE published
Severity critical, CVSS 9.8
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.