# CVE-2026-96228: SSL Wireless SMS Notification <= 3.8.1 - Unauthenticated Authentication Bypass to Account Takeover


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-qmqg-vj89-8937

## What is CVE-2026-96228?

CVE-2026-96228 is a high-severity vulnerability in sslplugins SSL Wireless SMS Notification, published on 29 Oct 2026. 

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-96228?


## How do I fix CVE-2026-96228?

No fix has been published for CVE-2026-96228 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96228 being exploited?

There is no known exploitation of CVE-2026-96228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96228 and fix it if it is affected.

What it is: CVE-2026-96228 is a high-severity vulnerability in sslplugins SSL Wireless SMS Notification, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-96228 in the wild and no public exploit code.

Affected product: sslplugins SSL Wireless SMS Notification. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96228/ (Markdown: https://insights.sbomify.com/CVE-2026-96228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96228
- OSV: https://osv.dev/vulnerability/CVE-2026-96228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96228/
Summaries are generated and may contain mistakes; the official description above is the record.