Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site with Payments module + dual PayPal/Stripe form
-
DeliverySubmit form with script in 'gateway' field
-
ExploitPayload stored unsanitized
-
ExecutionVictim loads injected page
-
ImpactScript executes in victim browser (S:C)
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 non-default configuration: the plugin's Payments module must be enabled AND a Contact Form 7 form must be configured to accept BOTH PayPal and Stripe as payment gateways simultaneously. Given that, the 'gateway' form field is injectable by an unauthenticated remote attacker (PR:N/UI:N) in versions ≤1.2.1, with the stored payload later executing when any user views the injected page. Limiting factors: the dual-gateway payments configuration is specific and unlikely to be the default for most installs, which substantially narrows the exploitable population; impact is confined to browser-context script execution (C:L/I:L, no availability impact). Patched in changeset 3713721 (versions after 1.2.1). |
| Impact | Signals are mixed and net out to low real-world priority despite the 7.2 'High' CVSS. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) scores highly largely because PR:N (unauthenticated) and S:C (scope change, typical of stored XSS that executes in other users' browser contexts) stack together; however, the impact sub-metrics are only C:L/I:L/A:N, reflecting limited script-driven impact rather than system compromise. No EPSS score was supplied, this CVE is not in CISA KEV, and no public exploit code was identified at time of analysis - so there is no evidence of active or automated exploitation. The decisive risk reducer is in the description itself: exploitation requires a specific non-default configuration (Payments module enabled AND a single form configured to accept BOTH PayPal and Stripe), which sharply narrows the exploitable population below what PR:N/AC:L alone would imply. Treat as a low-urgency, patch-on-cycle item: genuinely unauthenticated and network-reachable where the precondition holds, but gated by a narrow configuration and carrying only low confidentiality/integrity impact. No key signals conflict with the vector; the main caveat is the absence of EPSS/KEV/POC data, which is consistent with a newly disclosed, low-exploitation-interest plugin flaw. |
| Exploit ScenarioDerived | On a site running this plugin with the Payments module enabled and a Contact Form 7 form set to accept both PayPal and Stripe, an unauthenticated attacker submits a crafted 'gateway' form field containing a malicious script payload. Because input is insufficiently sanitized and output is not escaped, the payload is stored and later rendered, executing in the browser of any user (including an administrator) who views the affected page. No public proof-of-concept was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Unauthenticated stored cross-site scripting (XSS) in the WordPress plugin Business Essentials for Contact Form 7 (versions ≤1.2.1) allows remote attackers to inject arbitrary web scripts via the 'gateway' form field, which execute when a user views the injected page. Exploitation requires a non-default configuration-the plugin's Payments module must be enabled and a form must be set to accept both PayPal and Stripe as payment gateways-substantially narrowing the affected population. No public exploit code has been identified at time of analysis, and while the CVSS score is 7.2 (High), the specific prerequisites and limited browser-context impact (C:L/I:L, no availability impact) result in a low net real-world priority. A fix is available in plugin changeset 3713721 (versions after 1.2.1).
RemediationAI
Update the Business Essentials for Contact Form 7 plugin to a version later than 1.2.1; the fix is included in changeset 3713721 (https://plugins.trac.wordpress.org/changeset/3713721/cf7-redirect-thank-you-page). If immediate updating is not possible, disable the Payments module if payment processing is not required, or ensure that no form is configured to accept both PayPal and Stripe as payment gateways simultaneously-both measures eliminate the specific preconditions for exploitation, though they may break intended e-commerce functionality. Additionally, review the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/e6a60043-a060-472b-9b43-e82a4d2420b0?source=cve) for any updated guidance. No other mitigations are documented; general WordPress security best practices such as restricting plugin installation and using a web application firewall may provide defense in depth but do not address the root cause.
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 stored cross-site scripting issue arising from insufficient input sanitization and output escaping in the 'gateway' form field of the Business Essentials for Contact Form 7 plugin (plugin directory slug cf7-redirect-thank-you-page, CPE cpe:2.3:a:scottpaterson:business_essentials_for_contact_form_7). The plugin extends Contact Form 7 to add payment processing; the vulnerable code paths are in includes/modules/payments/redirect_methods.php, functions.php, and cpt.php. When the Payments module is active and a form is configured with both PayPal and Stripe gateways, the 'gateway' parameter is stored without proper encoding and later rendered unsafely, allowing an unauthenticated attacker (CVSS PR:N, UI:N) to persist arbitrary JavaScript. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) indicates a network-vector, no-privilege, no-interaction attack that changes scope (S:C) but has only low confidentiality and integrity impact and no availability impact.
Know when Business Essentials For Contact Form 7 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:N/S:C/C:L/I:L/A:N
Unauthenticated remote injection (PR:N/AV:N/AC:L - the config precondition gates targets but does not raise attacker effort); stored XSS executing in other users' context gives S:C with low C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Business Essentials for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'gateway' Form Field in all versions up to, and including, 1.2.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the Payments module to be enabled and a form to be configured to accept both PayPal and Stripe as payment gateways.
Executive ViewAI
WordPress sites running the Business Essentials for Contact Form 7 plugin at version 1.2.1 or earlier, with the Payments module enabled and forms configured to accept both PayPal and Stripe, are exposed to a stored cross-site scripting flaw rated CVSS 7.2 (High). Exploitation requires this non-default dual-gateway configuration, and the resulting impact is limited to partial loss of confidentiality and integrity in the visitor's browser with no availability impact, so the realistic set of affected pages and the severity of potential harm are both narrow. Leadership should care less about immediate incident risk and more about the fact that resolving this depends on knowing which web properties run the plugin and how their payment configurations are set, which is a patch-management and asset-visibility gap.
No vendor-released patch identified at time of analysis; the technical description references a fix in changeset 3713721 (versions after 1.2.1), which should be validated with the vendor before relying on it. Interim mitigations: disable the plugin's Payments module, remove the dual PayPal/Stripe gateway configuration so the 'gateway' field is not exposed, apply WAF or input filtering on the 'gateway' parameter, and enforce a Content Security Policy to limit script execution.
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-90574
GHSA-h887-w8fc-499x
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB