Skip to main content
VulnerabilityPublished

CVE-2026-115303: Contact Form by Supsystic (WordPress plugin) · CRLF Injection

Affects Contact Form by Supsystic (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low : upgrade to 1.11.1 when convenient.

Data as of 29 Oct 2026, 19:15 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (WPScan)CVSS 3.13.7
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Contact Form by SupsysticAffected
  • <1.11.1
Fixed in
  • 1.11.1

AI-suggested

Upgrade the Contact Form by Supsystic plugin to version 1.11.1 or later, where this vulnerability is fixed. No additional mitigation is required once the plugin is updated.

Description

The Contact Form by Supsystic WordPress plugin before 1.11.1 does not strip CR/LF characters or re-validate submitted field values before concatenating them into outgoing email headers when a form is configured to map a submitted field into its Reply-To, From or Cc header, allowing unauthenticated users to inject arbitrary email headers such as additional Bcc or Cc recipients into the notification email.

References

Community reviews

Loading reviews…