CVE-2026-96228
SSL Wireless SMS Notification for WordPress is vulnerable to …
SSL Wireless SMS Notification for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 3.8.1. The public final_login_ajax_action handler resolves a user and issues an authenticated session by matching the wp_sslcare_otp table on only the attacker-supplied phone and cap_data, without verifying the SMS OTP or any server-side single-use state. Because cap_data was chosen by the attacker in the public otp_login_ajax_action step (which stores the row before sending the SMS), the finalize step trivially matches and the user is looked up solely by the sslcare_login_phone meta. This makes it possible for unauthenticated attackers who know a phone-linked user's number to take over that account.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- plugins.svn.wordpress.org/ssl-wireless-sms-notification/tags/3.8.1/sslWireless.php
- www.wordfence.com/threat-intel/vulnerabilities/id/8e4947d5-91f3-4b36-b309-7c52c483be3d?sou
- www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/ssl-wireless-sms-notifica
- nvd.nist.gov/vuln/detail/CVE-2026-96228
- cve.org/CVERecord?id=CVE-2026-96228
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.