SSL Wireless SMS Notification <= 3.8.1 — Unauthenticated Authentication Bypass to Account Takeover
CVE-2026-96228Published · Updated Action summary
Affected: ≤3.8.1No patch available
What to do until a fix ships- Severity
- High8.1
- CVSS
- 8.1CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:HAttack complexity- High
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
- Weakness
- CWE-287 Improper Authentication
- Required access
- No account needed
- Exploit prediction (EPSS)
- 0.5% chance in 30 days41th percentile
- CISA KEV
- Not listed
On this page8
Am I affected?
SSL Wireless SMS Notification ssl-wireless-sms-notification
- Affected≤ 3.8.1
- PatchedNo fix yet
No patched version available.
You are affected if you run ≤ 3.8.1. No fixed version has been released.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under SSL Wireless SMS Notification.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch SSL Wireless SMS Notification to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to antaloaalonso.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in SSL Wireless SMS Notification
All 3| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.5 | Unauthenticated SQL Injection ≤3.5.0Update to 3.6.0 | CVE-2024-56284 | |
| Critical9.8 | Unauthenticated Privilege Escalation ≤3.6.0Update to 3.7.0 | CVE-2024-56220 |
- High7.5Unauthenticated SQL Injection
≤3.5.0Update to 3.6.0
- Critical9.8Unauthenticated Privilege Escalation
≤3.6.0Update to 3.7.0
Timeline
CVE published
Severity high, CVSS 8.1
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- EPSS
- Exploit Prediction Scoring System by FIRST.org.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.