Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94256 Overview
CVE-2026-94256 is an authentication bypass vulnerability in the SMS Alert WordPress plugin versions prior to 4.0.1. The plugin fails to verify that the account attempting to log in matches the account tied to the verified one-time code (OTP). Unauthenticated attackers can log in as any user with a stored phone number, including administrators, by completing the OTP challenge on a phone they control. The weakness is categorized under [CWE-287: Improper Authentication].
Critical Impact
Attackers can gain administrator-level access to WordPress sites running the vulnerable SMS Alert plugin, leading to full site compromise.
Affected Products
- SMS Alert WordPress plugin versions prior to 4.0.1
- WordPress installations with the SMS Alert plugin configured for login/OTP flows
- Any WordPress user account with a stored phone number in the plugin
Discovery Timeline
- 2026-10-10 - CVE-2026-94256 published to the National Vulnerability Database
- 2026-10-13 - Last updated in the NVD database
Technical Details for CVE-2026-94256
Vulnerability Analysis
The SMS Alert plugin implements an OTP-based login flow that sends a verification code to a user's registered phone number. The flow is intended to confirm that the person logging in controls the phone number tied to the target account. In vulnerable versions, the server-side verification step confirms only that the submitted code is valid for some phone number, not that it belongs to the account being authenticated.
An attacker supplies their own phone number during the challenge, completes the OTP step successfully, and then requests authentication for a different username such as admin. The plugin issues a session for that account because the OTP state is not bound to the account context. This produces full authentication bypass against any WordPress user whose record includes a stored phone number.
The issue is a business-logic authentication flaw rather than a memory-safety or injection bug. It affects confidentiality, integrity, and availability of the WordPress site because an administrator takeover permits plugin installation, content modification, and user data access.
Root Cause
The root cause is a missing identity binding between the OTP verification state and the target user account. The plugin treats "the submitted code matches a code we sent" as equivalent to "this request is authorized to log in as the requested account." Correct implementations must verify that the account tied to the verified OTP is the same account being signed in.
Attack Vector
The attack is remote and requires no prior authentication. An attacker needs a phone number that the plugin accepts and knowledge of a target username. The attacker initiates the OTP flow against their own phone, submits the valid code, and then triggers the login call referencing the victim account. The attack complexity is elevated because the attacker must understand the request sequence and have a valid phone-bound account entry in the target instance.
The vulnerability is a business-logic flaw and does not require a code payload. Refer to the WPScan Vulnerability Report for request-level details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-94256
Indicators of Compromise
- Successful WordPress logins for privileged accounts (administrator, editor) that are not preceded by a corresponding password-reset or standard login event.
- OTP verification requests originating from IP addresses or user agents that differ from the account's normal login telemetry.
- Creation of new administrator accounts, plugin installations, or theme file edits shortly after an SMS Alert OTP exchange.
- Multiple OTP requests from a single source referencing different usernames in rapid succession.
Detection Strategies
- Correlate SMS Alert plugin OTP challenge events with the WordPress wp_login action and alert when the phone number used for OTP does not match the stored number on the authenticated account.
- Deploy web application firewall rules that inspect requests to the SMS Alert login endpoints and flag mismatches between the OTP session identifier and the submitted user_login parameter.
- Hunt in access logs for POST requests to the plugin's login handler followed by /wp-admin/ sessions established from the same source within seconds.
Monitoring Recommendations
- Enable WordPress audit logging to capture authentication events, user role changes, and plugin modifications.
- Forward web server and WordPress audit logs to a centralized SIEM for correlation with network telemetry.
- Alert on first-time administrator logins from new geolocations or ASNs following an OTP code challenge.
How to Mitigate CVE-2026-94256
Immediate Actions Required
- Upgrade the SMS Alert WordPress plugin to version 4.0.1 or later on all affected sites.
- Audit WordPress user accounts for unauthorized administrators, unexpected role changes, and unknown plugin installations.
- Rotate passwords and invalidate active sessions for all privileged accounts following the upgrade.
- Review WordPress and web server logs for suspicious OTP activity dating back to the plugin's installation.
Patch Information
The vendor fixed CVE-2026-94256 in SMS Alert plugin version 4.0.1. The patch binds the OTP verification state to the specific user account tied to the stored phone number, so a login request for a different account fails. Administrators should apply the update through the WordPress plugin management interface or via WP-CLI. See the WPScan Vulnerability Report for the authoritative advisory.
Workarounds
- Disable the SMS Alert plugin until the upgrade to 4.0.1 can be verified in a staging environment.
- Remove stored phone numbers from administrator and editor accounts to prevent OTP-based login against those accounts.
- Restrict /wp-admin/ and the plugin's login endpoint by source IP using a reverse proxy or WAF while remediation is pending.
- Enforce an additional authentication factor at the reverse proxy or hosting layer, independent of the plugin.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

