Skip to main content

Login with Phone Number CVE-2026-65570

| EUVDEUVD-2026-53988 HIGH
Authentication Bypass by Spoofing (CWE-290)
2026-08-06 Patchstack GHSA-mhqm-xpwx-j9xw
8.1
CVSS 3.1 · Vendor: Patchstack
Share

Severity by source

Vendor (Patchstack) PRIMARY
8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.1 HIGH

Network-reachable, unauthenticated, but AC:H reflects the capture-replay precondition; full CIA impact from account takeover is warranted.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Aug 06, 2026 - 15:50 vuln.today
CVE Published
Aug 06, 2026 - 14:27 cve.org
HIGH 8.1

DescriptionCVE.org

Unauthenticated Bypass Vulnerability in Login with phone number <= 1.8.70 versions.

AnalysisAI

Authentication bypass in the Login with Phone Number WordPress plugin (≤1.8.70) allows remote, unauthenticated attackers to circumvent the login mechanism via an authentication capture-replay technique (CWE-290), achieving full account takeover with high confidentiality, integrity, and availability impact. Exploitation carries high attack complexity (CVSS AC:H), meaning a specific race condition, token-interception window, or knowledge of a registered phone number is likely required. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface is any internet-accessible WordPress site running the affected plugin.

Technical ContextAI

The affected component is the 'Login with Phone Number' WordPress plugin authored by Hamid Alinia (CPE: cpe:2.3:a:hamid_alinia:login_with_phone_number:*:*:*:*:*:*:*:*), which replaces or supplements WordPress's default password-based login with an OTP or token sent to a mobile phone number. CWE-290 (Authentication Bypass by Capture-Replay) indicates the root cause is the plugin's failure to adequately protect the authentication token - an attacker can intercept or predict the one-time credential, then replay it to authenticate as the targeted user. This class of flaw typically arises from insufficient token entropy, missing expiry enforcement, lack of binding the token to a device or session, or predictable token generation logic within the SMS/OTP workflow.

RemediationAI

Update the Login with Phone Number plugin immediately to a version above 1.8.70 once a patched release is confirmed available in the WordPress plugin repository - no specific fixed version number was provided in the available intelligence, so administrators should monitor the plugin's changelog and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/login-with-phone-number/vulnerability/wordpress-login-with-phone-number-plugin-1-8-70-bypass-vulnerability-vulnerability for confirmation of a fix. As an interim compensating control, deactivating or removing the plugin and reverting to WordPress's native password-based login eliminates the attack surface entirely, at the trade-off of disrupting phone-number-based login for users. If deactivation is not operationally feasible, restricting the WordPress login endpoint (wp-login.php) to trusted IP ranges via web server rules or a WAF rule targeting the phone-login flow reduces remote exploitability, though it does not eliminate the underlying flaw. Enabling multi-factor authentication on high-privilege accounts via a separate plugin provides defense-in-depth if the plugin must remain active.

Share

CVE-2026-65570 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy