WordPress plugin · login-with-phone-number
Is OTP Login With Phone Number, OTP Verification safe?
Safe on 1.8.79 or newer.
The current version, 1.8.79, is past every affected range on record (17 of 17 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 17
- High or critical
- 12
- Exploited
- none
- Current version
- 1.8.79
- Last updated
- Oct 24, 2026
- Active installs
- 1,000+
Every recorded flaw
- Oct 18, 2026Login with phone number: Incorrect Privilege AssignmentCVE-2026-110373 · affects up to 1.8.77 · reported by PatchstackHigh 8.1
- Oct 15, 2026Login with phone number: Missing AuthorizationCVE-2026-110374 · affects up to 1.8.77 · reported by PatchstackMedium 4.3
- Aug 6, 2026Unauthenticated Bypass Vulnerability in Login with phone number <= 1.8.70 versions.CVE-2026-65570 · affects up to 1.8.70 · reported by PatchstackHigh 8.1
- Aug 5, 2026OTP Login With Phone Number, OTP Verification: Does not limit the number of OTP verification attempts or invalidate a one-time login code after a wrong guessCVE-2026-15210 · fixed in 1.8.71 · reported by WPScanCritical 9.1
- May 29, 2026OTP Login With Phone Number, OTP Verification: Authentication bypassCVE-2026-3655 · affects up to 1.8.60 · reported by WordfenceCritical 9.8
- Aug 31, 2025Login with phone number: Missing AuthorizationCVE-2024-32832 · affects up to 1.6.93 · reported by PatchstackCritical 9.8
- Aug 14, 2025WooCommerce OTP Login With Phone Number, OTP Verification: Authentication bypassCVE-2025-8342 · affects up to 1.8.47 · reported by WordfenceHigh 8.1
- Sep 14, 2024Login with phone number: Privilege escalationCVE-2024-6482 · affects up to 1.7.49 · reported by WordfenceHigh 8.8
- Jul 22, 2024Login with phone number: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2024-37429 · affects up to 1.7.35 · reported by PatchstackMedium 5.9
- Jun 18, 2024Login with phone number: Unauthorized password resetsCVE-2024-6125 · affects up to 1.7.34 · reported by WordfenceHigh 8.1
- May 28, 2024Login with phone number: Authentication bypassCVE-2024-5150 · affects up to 1.7.26 · fixed in 1.7.27 · reported by WordfenceCritical 9.8
- May 17, 2024Login with phone number: Incorrect Privilege AssignmentCVE-2024-32507 · affects up to 1.7.16 · reported by PatchstackHigh 8.8
- May 6, 2024Login with phone number: Missing AuthorizationCVE-2024-34371 · affects up to 1.7.18 · reported by PatchstackMedium 4.3
- Apr 15, 2024Login with phone number: Cross-Site Request Forgery (CSRF)CVE-2024-31424 · affects up to 1.6.93 · reported by PatchstackHigh 8.8
- Sep 12, 2023Login with phone number: Cross-Site Request ForgeryCVE-2023-4916 · affects up to 1.5.6 · reported by WordfenceHigh 8.8
- Aug 1, 2022Login with phone number: Does not sanitise and escape plugin settingsCVE-2022-0598 · fixed in 1.3.8 · reported by WPScanMedium 4.8
- Mar 14, 2022Login with phone number: Includes a file deleteCVE-2022-0593 · fixed in 1.3.7 · reported by WPScan1.4% oddsMedium 6.5
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.