The Contact Form by Supsystic WordPress plugin before 1.11.1 does not validate a CSRF token or request origin on two
Source GCVE Database
Not known to be exploited : upgrade to 1.11.1 soon.
Data as of 29 Oct 2026, 07:12 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 1.11.1
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 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 29 Oct 2026.
What to do
Upgrade Contact Form by Supsystic (WordPress plugin) to 1.11.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Contact Form by Supsystic | Affected
| Fixed in
|
AI-suggested
A fixed version 1.11.1 or later should be applied once available. Until patched, administrators should avoid clicking on untrusted links or performing form management actions from untrusted sources to reduce risk of CSRF exploitation.
Description
The Contact Form by Supsystic WordPress plugin versions before 1.11.1 lack validation of CSRF tokens or request origin on two administrator-only actions: bulk deletion of captured form submissions and wiping a form's statistics. This vulnerability allows attackers to trick logged-in administrators into sending forged requests that permanently delete stored contact leads and analytics data.