Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft URL with XSS payload in data tag param
-
DeliveryDeliver link via phishing to site user
-
ExploitVictim clicks, plugin reflects payload unescaped
-
ExecutionScript executes in victim browser session
-
ImpactSteal session/perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a page on the target site that renders the MC4WP 'data' dynamic content tag (via the plugin's dynamic-content/form-tag handling in class-dynamic-content-tags.php / class-form-tags.php) so that attacker-controlled request input is reflected into the page. The attacker is unauthenticated (PR:N) but MUST trick a user into clicking a crafted link or performing an action (UI:R) - this is reflected, not stored/persistent, so there is no unattended mass-exploitation path. Impact is limited to script execution in the victim's browser (C:L/I:L); limiting factors are the required user interaction, the need for a form/page using the affected dynamic tag, and that all versions up to and including 4.14.0 are affected while 4.14.1 remediates it. |
| Impact | This is a real but bounded issue. The CVSS 3.1 base score of 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) is the canonical profile for a reflected XSS: network-reachable, low complexity, no privileges (PR:N confirms unauthenticated), but requiring victim user interaction (UI:R) and yielding only limited confidentiality/integrity impact (C:L/I:L) with a scope change (S:C) reflecting script execution in the victim's browser context rather than the server. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so exploitation status is 'no public exploit identified at time of analysis.' Reflected XSS is not automatable at scale (each hit needs a separately social-engineered victim), which is why such flaws rarely reach KEV despite being genuinely exploitable. Net: prioritize patching because the affected plugin is extremely widely deployed and the flaw is unauthenticated, but treat it as a moderate - not critical - priority; there is no evidence of active or automated exploitation. The reporting source (Wordfence) and the trac changeset showing the fix (4.14.1) corroborate the vulnerability and patch, so the core facts are well-supported. |
| Exploit ScenarioDerived | An attacker crafts a URL pointing at a page containing an MC4WP form that renders the 'data' dynamic content tag, embedding a malicious script payload in the request parameter that the tag reflects unsanitized. The attacker distributes this link via phishing or a malicious post; when a logged-in administrator or any visitor clicks it, the script executes in their browser session in the site's origin, enabling session/cookie theft or admin-action forgery. No public POC was identified, and successful exploitation depends on the victim performing the interaction (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 19, 2026
Reflected cross-site scripting in the MC4WP: Mailchimp for WordPress plugin through version 4.14.0 lets remote attackers inject arbitrary JavaScript into pages that render the plugin's 'data' dynamic content tag, executing in the browser of any user persuaded to click a crafted link. The weakness is insufficient input sanitization and output escaping in the plugin's dynamic-content and form-tag handling, rated CVSS 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N); exploitation is unauthenticated but requires user interaction and a page or form that actually uses the affected tag, so there is no unattended mass-exploitation path. Vendor-released patch: 4.14.1. No public exploit code and no confirmed active exploitation were identified at time of analysis; the issue is real but bounded.
RemediationAI
Upgrade the MC4WP: Mailchimp for WordPress plugin to version 4.14.1 or later, which is the vendor-released patch; the WordPress.org changesets listed in the references (diffing tag 4.14.0 against 4.14.1) document the sanitization and escaping corrections in the dynamic content tag and form tag code. Patch verification should confirm that includes/class-dynamic-content-tags.php and includes/forms/class-form-tags.php no longer reflect request input unescaped, since the plugin updates through the standard WordPress admin or WP-CLI (wp plugin update mailchimp-for-wp). If immediate upgrade is not possible, the practical compensating control is to stop rendering the affected surface: remove or disable any page, form, or template that uses the plugin's 'data' dynamic content tag until the update is applied, accepting the loss of that dynamic content functionality on those pages. Additional layered mitigations with their trade-offs include deploying a WAF rule that blocks script-bearing payloads in query parameters reaching pages containing Mailchimp form markup (trade-off: potential false positives on legitimate parameter values and no protection if the injection vector shifts), and setting a restrictive Content-Security-Policy that disallows inline script (trade-off: frequently breaks third-party and theme scripts unless carefully nonce-managed). Because exploitation requires the victim to click a crafted link, user awareness of unsolicited links to the affected site is helpful but is not a substitute for patching. Consult the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/ee4f837a-d0b5-48df-8c96-2a294985612e for the authoritative fix details.
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 vulnerability is a classic CWE-79 cross-site scripting flaw rooted in the plugin's dynamic content tag engine, implemented in includes/class-dynamic-content-tags.php (referenced at line 127) and the form tag handling in includes/forms/class-form-tags.php (lines 57 and 109). Dynamic content tags are shortcode-style placeholders that the plugin substitutes at render time, and the 'data' tag path fails to sanitize attacker-supplied request input before reflecting it back into the generated page markup, with no output escaping applied at the point of emission. Because the data never persists server-side, this is reflected XSS rather than stored XSS, and the CVSS scope change (S:C) reflects that the injected script executes in the context of the victim's browser session against the hosting site's origin, potentially reaching cookies, session tokens, or authenticated UI actions. The affected CPE is cpe:2.3:a:dvankooten:mc4wp:_mailchimp_for_wordpress, covering the 4.x line maintained by vendor dvankooten; the flaw was reported by Wordfence and mirrored through the CVE.org reference set.
Know when Mc4Wp 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:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Unauthenticated reflected XSS reachable over the network with low complexity but requiring victim interaction (UI:R); browser-context execution crosses scope (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The MC4WP: Mailchimp for WordPress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via 'data' Dynamic Content Tag in all versions up to, and including, 4.14.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-83559
GHSA-fhmr-f2rv-cv78
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB