{
  "id": "CVE-2026-96228",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-96228",
  "published_at": "2026-10-29T03:39:15.43Z",
  "title": "SSL Wireless SMS Notification \u003c= 3.8.1 - Unauthenticated Authentication Bypass to Account Takeover",
  "vendor": "sslplugins",
  "product": "SSL Wireless SMS Notification",
  "cvss": {
    "score": 8.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-287",
  "cvss_by_source": {
    "cna": 8.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "sslplugins",
        "product": "SSL Wireless SMS Notification",
        "ranges": [
          "\u003c= 3.8.1"
        ],
        "fixed_in": null
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
