Radar sectionsDatabase
Check my site
WordPress plugin

Contact Form by Supsystic <= 1.11.0 — Unauthenticated Arbitrary Email Header Injection

CVE-2026-115303Published · Updated

Action summary

Affected: ≤1.11.0Update to 1.11.1 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-93 Improper Neutralization of CRLF Sequences
Required access
No account needed
Exploit prediction (EPSS)
0.2% chance in 30 days13th percentile
CISA KEV
Not listed

Am I affected?

Contact Form by Supsystic – Drag & Drop Form Builder with Templates & Form Statistics contact-form-by-supsystic

  1. Affected≤ 1.11.0
  2. Patched in1.11.1

Update to 1.11.1 or newer.

You are affected if you run ≤ 1.11.0. Version 1.11.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Contact Form by Supsystic – Drag & Drop Form Builder with Templates & Form Statistics.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.11.1, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Contact Form by Supsystic – Drag & Drop Form Builder with Templates & Form Statistics to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Emirhan Sevmez.

The Contact Form by Supsystic plugin for WordPress is vulnerable to Email Header Injection in all versions up to, and including, 1.11.0. This is due to missing sanitization of CR/LF characters in user-controlled field values before concatenating them into outgoing email headers via utilsCfs::replaceVariables(). This makes it possible for unauthenticated attackers to inject arbitrary email headers, such as additional Bcc or Cc recipients, into outgoing notification emails sent by any configured contact form. A form must be configured to map a submitted field value into the Reply-To, From, or Cc email header.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Contact Form by Supsystic – Drag & Drop Form Builder with Templates & Form Statistics

All 21
More vulnerabilities in Contact Form by Supsystic – Drag & Drop Form Builder with Templates & Form Statistics
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
≤1.10.5Update to 1.10.7
CVE-2026-115591
Medium5.3Missing Authorization
≤1.10.7Update to 1.11.1
CVE-2026-115595
High7.2Authenticated (Administrator+) Remote Code Execution
≤1.11.0Update to 1.11.1
CVE-2026-115301
Medium5.3Missing Authorization
≤1.11.0Update to 1.11.1
CVE-2026-115302
Medium4.3Cross-Site Request Forgery
≤1.11.0Update to 1.11.1
CVE-2026-115300

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?