The Contact Form by Supsystic WordPress plugin before 1.11.1 does not verify a CSRF nonce before saving its mail
Source GCVE Database
Not known to be exploited : upgrade to 1.11.1 soon.
Data as of 29 Oct 2026, 07:10 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
Upgrade the Contact Form by Supsystic WordPress plugin to version 1.11.1 or later, where the CSRF nonce verification before saving mail settings is implemented. If you cannot patch yet, avoid visiting untrusted or suspicious pages while logged in as an administrator to reduce the risk of CSRF exploitation.
Description
The Contact Form by Supsystic WordPress plugin versions before 1.11.1 lack verification of a CSRF nonce when saving mail settings. This vulnerability allows an attacker to trick a logged-in administrator into visiting a crafted page, resulting in the overwriting of the site's outbound mail configuration, including SMTP server details, credentials, and notification recipients. This can enable the attacker to route contact form notifications through infrastructure they control.