HomeWordPress vulnerabilitiesOTP Login With Phone Number, OTP Verification
OTP Login With Phone Number, OTP Verification vulnerabilities
OTP Login With Phone Number, OTP Verification has 10 known vulnerabilities in this database. The most recent published record is dated 5 Aug 2026.
- Known vulnerabilities
- 10
- Active installs
- 1,000+
- Latest version
- 1.8.74
- Last updated
- 13 Sep 2026
- Most recent
- 5 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2026-15210 | Critical 9.1 | Before 1.8.71 | Fixed in 1.8.71 | 5 Aug 2026 |
| Authentication bypass CVE-2026-3655 | Critical 9.8 | Up to 1.8.60 | Fixed in a later version (latest 1.8.74) | 29 May 2026 |
| Authentication bypass CVE-2025-8342 | High 8.1 | Up to 1.8.47 | Fixed in a later version (latest 1.8.74) | 15 Aug 2025 |
| Privilege escalation CVE-2024-6482 | High 8.8 | Before 1.7.50 | Fixed in 1.7.50 | 14 Sep 2024 |
| Broken access control CVE-2024-6125 | High 8.1 | Up to 1.7.34 | Fixed in a later version (latest 1.8.74) | 19 Jun 2024 |
| Authentication bypass CVE-2024-5150 | Critical 9.8 | Up to 1.7.26 | Fixed in a later version (latest 1.8.74) | 29 May 2024 |
| Cross-site request forgery (CSRF) CVE-2023-4916 | High 8.8 | Up to 1.5.6 | Fixed in a later version (latest 1.8.74) | 13 Sep 2023 |
| SQL injection CVE-2023-23492 | High 8.8 | Before 1.4.2 | Fixed in 1.4.2 | 20 Jan 2023 |
| Cross-site scripting (XSS) CVE-2022-0598 | Medium 4.8 | Up to 1.3.7 | Fixed in a later version (latest 1.8.74) | 1 Aug 2022 |
| Denial of service CVE-2022-0593 | Medium 6.5 | Before 1.3.7 | Fixed in 1.3.7 | 14 Mar 2022 |
Read the published descriptions
- CVE-2026-15210, 5 Aug 2026
- The OTP Login With Phone Number, OTP Verification WordPress plugin before 1.8.71 does not limit the number of OTP verification attempts or invalidate a one-time login code after a wrong guess, and an unauthenticated user can request a login code for any account. Because the code is a short numeric OTP, an attacker can brute-force it and take over any account, including an administrator's. CVE record
- CVE-2026-3655, 29 May 2026
- The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass in versions 1.8.50 through 1.8.60. This is due to the Firebase verification flow in the `lwp_ajax_register` AJAX handler not binding the Firebase session to the phone number supplied in the request. The `idehweb_lwp_activate_through_firebase()` function validates that a Firebase OTP session is legitimate, but the `phoneNumber` returned by Firebase is never compared against the victim's stored phone number. This makes it possible for unauthenticated attackers to authenticate as any user who has a phone number stored in user meta, including administrators, by verifying their own Firebase session and supplying the victim's phone number in the same request. CVE record
- CVE-2025-8342, 15 Aug 2025
- The WooCommerce OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass due to insufficient empty value checking in the lwp_ajax_register function in all versions up to, and including, 1.8.47. This makes it possible for unauthenticated attackers to bypass OTP verification and gain administrative access to any user account with a configured phone number by exploiting improper Firebase API error handling when the Firebase API key is not configured. CVE record
- CVE-2024-6482, 14 Sep 2024
- 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. CVE record
- CVE-2024-6125, 19 Jun 2024
- 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. CVE record
- CVE-2024-5150, 29 May 2024
- 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. CVE record
- CVE-2023-4916, 13 Sep 2023
- The Login with phone number plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.6. This is due to missing nonce validation on the 'lwp_update_password_action' function. This makes it possible for unauthenticated attackers to change user password via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2023-23492, 20 Jan 2023
- The Login with Phone Number WordPress Plugin, version < 1.4.2, is affected by an authenticated SQL injection vulnerability in the 'ID' parameter of its 'lwp_forgot_password' action. CVE record
- CVE-2022-0598, 1 Aug 2022
- The Login with phone number WordPress plugin before 1.3.8 does not sanitise and escape plugin settings which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed. CVE record
- CVE-2022-0593, 14 Mar 2022
- The Login with phone number WordPress plugin before 1.3.7 includes a file delete.php with no form of authentication or authorization checks placed in the plugin directory, allowing unauthenticated user to remotely delete the plugin files leading to a potential Denial of Service situation. CVE record
What to do if you run OTP Login With Phone Number, OTP Verification
If you run OTP Login With Phone Number, OTP Verification, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new OTP Login With Phone Number, OTP Verification vulnerabilities
Free. We email you when a new vulnerability is published for OTP Login With Phone Number, OTP Verification, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.