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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
sslplugins:ssl wireless sms notification
References 3
https://plugins.svn.wordpress.org/ssl-wireless-sms-notification/tags/3.8.1/sslW…
security@wordfence.com
https://www.wordfence.com/threat-intel/vulnerabilities/id/8e4947d5-91f3-4b36-b3…
security@wordfence.com
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/ssl-wi…
security@wordfence.com