Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit contact form with CRLF-laced field value
-
ExploitValue concatenated into email headers unsanitized
-
ImpactInject additional Bcc/Cc recipients into notification email
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization CRLF sequence sanitization
|
| Exploitation Conditions | Exploitable only when a form is explicitly configured to map a user-submitted field value into its Reply-To, From or Cc email header - this header-mapping configuration is the required, non-default precondition and is what limits exploitation. Given that configuration, exploitation is remote and unauthenticated (PR:N/UI:N): any visitor who can submit the form can inject headers, with no login or user interaction by a victim required. Forms that do not map submitted input into those headers are not affected. Impact is limited to manipulating outgoing notification email headers (e.g. adding Bcc/Cc recipients); affected versions are those before 1.11.1, fixed in 1.11.1. |
| Impact | This is a genuinely low-priority issue by every available signal, and the signals are mutually consistent rather than conflicting. The CVSS 3.1 base score is 3.7 (Low) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N: network-reachable and unauthenticated (PR:N), but high attack complexity (AC:H) and limited to a low integrity impact (I:L) with no confidentiality or availability impact. The limited impact fits the mechanism - injection of extra email headers (e.g. Bcc/Cc) into an outgoing notification email, which tampers with message content/routing but does not disclose protected data or run code. The vuln.today decision label is 'monitor', not act_now or emergency. It is NOT in CISA KEV, and no EPSS score was supplied, so widespread or active exploitation is not indicated. A public PoC reference exists (WPScan) but it is not verified as working exploit code. The AC:H rating is plausibly explained by the exploitation precondition stated in the description (the form must be configured to map a submitted field into a Reply-To/From/Cc header); however, the sources do not explicitly state why AC:H was assigned, so that linkage is inferred, not confirmed. Net: a real but minor header-injection flaw, appropriate to patch on a normal maintenance cycle rather than as an emergency. |
| Exploit ScenarioDerived | An unauthenticated visitor submits the public contact form on a site where an admin has mapped a submitted field (e.g. the sender address) into the email's Reply-To, From or Cc header, embedding CR/LF sequences and extra header lines in that field. The plugin concatenates the unsanitized value into the outgoing notification email headers, so the attacker silently adds Bcc/Cc recipients or otherwise manipulates headers. A public PoC reference exists (WPScan) but is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Email header injection in the Supsystic Contact Form plugin for WordPress (versions before 1.11.1) lets unauthenticated visitors append extra recipients such as Bcc or Cc to outgoing notification emails, but only on sites where an administrator has deliberately configured a form to place a submitted field value into the Reply-To, From or Cc header. That header-mapping configuration is a non-default precondition, so forms using fixed, administrator-defined addresses are not affected, and the demonstrated impact is limited to manipulation of notification email headers rather than code execution or data disclosure. Severity is low (CVSS 3.7, high attack complexity, no confidentiality or availability impact); there is no CISA KEV entry, and the only exploitation reference is a public PoC reference that is not verified as working exploit code, which aligns with the monitor-level priority assigned to this issue.
RemediationAI
Upgrade the Contact Form by Supsystic plugin to version 1.11.1 or later, which is the release that resolves this issue; the WPScan advisory at https://wpscan.com/vulnerability/c32e3ccd-84cb-42a4-a343-353a02ccb541/ is the reference for confirming the fixed version. Where an immediate update is not possible, the effective compensating control is configuration-level: stop mapping user-submitted fields into the Reply-To, From or Cc headers and use fixed, administrator-defined addresses for those headers instead, keeping submitted values in the message body. The trade-off is a loss of the reply-to-submitter convenience, since replies then go to the site's configured address rather than to the person who submitted the form, and any existing forms relying on that mapping must be edited individually. Because exploitation requires this mapping to be present, sites that never enabled it do not need emergency action and can schedule the update normally.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a WordPress plugin that builds outbound notification emails with PHP's mail functions, concatenating administrator-selected form field values into raw header strings. Because CR/LF sequences in those values are neither stripped nor re-validated before the concatenation, a submitter can terminate the intended header line and introduce additional header lines, the class of flaw commonly described as email header or CRLF injection. In this plugin the flaw is reachable only through a specific administrative configuration: the form must map a user-submitted field into its Reply-To, From or Cc header. Where that mapping is absent, submitted values flow only into the message body and the injection path does not exist. Given the mapping, the attack is remote and unauthenticated (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) - any visitor able to submit the form can attempt it, with no victim interaction - and the consequence is modification of the outgoing notification message (for example adding recipients), reflected as low integrity impact. The provided CPE string carries an unknown vendor and a wildcard version, so exact build-level fingerprinting should rely on the plugin's version number rather than CPE matching; affected releases are those below 1.11.1. The trigger mechanics beyond the header-mapping precondition are not described in the available sources.
Know when Contact Form By Supsystic gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Remote unauthenticated form submission (AV:N/PR:N/UI:N); AC:H reflects the required non-default header-mapping configuration; only integrity of outgoing email headers is affected (I:L), no C or A impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
More in Contact Form By Supsystic
View allRemote code execution in Contact Form by Supsystic plugin for WordPress (all versions ≤1.7.36) allows unauthenticated at
Stored server-side template injection in the WordPress plugin Contact Form by Supsystic before 1.11.1 lets a WordPress a
Cross-site request forgery in the Supsystic Contact Form plugin for WordPress before 1.11.1 lets an attacker overwrite a
Unauthenticated deletion of stored form statistics is possible in the Contact Form by Supsystic WordPress plugin before
Cross-site request forgery in the WordPress plugin Contact Form by Supsystic before 1.11.1 lets an attacker permanently
Stored cross-site scripting in the Contact Form by Supsystic WordPress plugin before 1.8.0 lets users with access to the
Unauthenticated information disclosure in the Supsystic Contact Form WordPress plugin (all versions through 1.10.5) lets
Stored cross-site scripting in the Contact Form by Supsystic WordPress plugin (all versions ≤1.10.2) allows unauthentica
Unauthenticated cross-site scripting in Contact Form by Supsystic WordPress plugin (all versions before 1.10.0) allows a
Unauthenticated authentication bypass in the Contact Form by Supsystic WordPress plugin (versions before 1.10.0) exposes
Missing authorization (CWE-862) in the WordPress plugin Contact Form by Supsystic, affecting all versions through 1.10.7
EUVD-2026-112675
GHSA-ghmm-gqr3-xwc7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB