Improper authentication in SMS Alert
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-287.
Summary
The SMS Alert WordPress plugin before 3.9.8 does not bind its "mobile verified" session flag to the phone number that was actually verified: after an attacker verifies an OTP sent to their own phone, the signup/login handler reads a fresh, attacker-supplied phone number to select the account and logs them in. An unauthenticated attacker can therefore log in as any user, including an administrator, who has a billing phone on file.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | SMS Alert | before 3.9.8 | 3.9.8 | Patch available | CNA |
- SMS Alert VendorUnknown Affected before 3.9.8 Fixed in 3.9.8 Patch available CNA
Remediation
- Fix · CNA SMS Alert (Unknown) Fixed in 3.9.8
Timeline
- 2026-10-02 Threatist record created from CVE-2026-15206
- 2026-10-03 Alias added: GHSA-63jw-46hv-gwp2
References
Sources
- CVE-2026-15206 · CVE Program
- CVE-2026-15206 · NVD
- FIRST EPSS
- GHSA-63jw-46hv-gwp2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences