The SMS Alert WordPress plugin before 4.0.4 does not sanitise and escape a parameter before using it in a SQL
Source GCVE Database
Not known to be exploited : upgrade to 4.0.4 soon.
Data as of 22 Nov 2026, 07:27 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.0.4
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade SMS Alert (WordPress plugin) to 4.0.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SMS Alert | Affected
| Fixed in
|
AI-suggested
Upgrade the SMS Alert WordPress plugin to version 4.0.4 or later, where this SQL injection vulnerability has been addressed. No other mitigation guidance is provided.
Description
The SMS Alert WordPress plugin versions before 4.0.4 contain a SQL injection vulnerability due to improper sanitization and escaping of a parameter used in a SQL statement. This flaw can be exploited by users with administrator privileges.