Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account
-
DeliveryInject XSS payload via plugin field
-
ExploitAdmin views injected content
-
ExecutionScript executes in admin browser
-
ImpactSession hijack or privileged action
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 an authenticated account with at least Contributor privileges on a WordPress site running Ultimate Addons for Contact Form 7 <= 3.5.50 (PR:L), plus subsequent user interaction (UI:R) - a higher-privileged user such as an admin or editor must view the attacker-injected content for the stored script to execute. This limits realistic impact to sites that allow untrusted Contributor-level registration; it is not exploitable pre-authentication or against a site where no privileged user renders the malicious content. |
| Impact | This is a moderate-priority, not high-priority, issue. The CVSS 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) rests on network vector but is materially gated by PR:L and UI:R: the attacker must already hold a Contributor-level account on the target WordPress site, and an admin/editor must subsequently view the injected content for the script to fire. The scope change (S:C) reflects that a Contributor-stored payload executes in a higher-privileged user's browser (the classic WP admin-context XSS boundary crossing), which is the main reason this scores above 5. No EPSS score, no CISA KEV listing, and no public POC are provided - exploitation status is therefore 'no public exploit identified at time of analysis,' meaning this is not evidence of widespread or automated exploitation. I question the A:L component: a reflected/stored XSS of this class does not credibly degrade availability, so a defensible vector is A:N, dropping the real score to roughly 6.4. Net: a real but authenticated, interaction-dependent flaw - patch it in routine cycles, not as an emergency. |
| Exploit ScenarioDerived | An attacker who has registered or obtained a Contributor account on a WordPress site running Ultimate Addons for Contact Form 7 <= 3.5.50 injects a malicious script payload into a plugin-controlled field. When an administrator or editor later views that content in wp-admin, the script executes in their authenticated browser session, enabling actions such as session/cookie theft or forged admin requests. No public POC or active exploitation is reported at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Stored cross-site scripting in Ultimate Addons for Contact Form 7 (all versions through 3.5.50) allows an authenticated user with Contributor-level access to inject script into plugin-rendered content that later executes in the browser of a higher-privileged user such as an administrator or editor who views that content. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, base 6.5 per the vendor score) requires both a low-privileged account and victim interaction, so realistic exposure is limited to WordPress sites that grant Contributor accounts to untrusted parties; there is no identified pre-authentication path. No public exploit code and no CISA KEV entry were identified at time of analysis, making this a moderate-priority rather than high-priority issue, though the scope-change characteristic means injected script can act outside the plugin's own origin context within the site.
RemediationAI
No vendor-released patch or fixed version was identified in the available data at time of analysis, so the first step is to confirm the current status against the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/ultimate-addons-for-contact-form-7/vulnerability/wordpress-ultimate-addons-for-contact-form-7-plugin-3-5-50-cross-site-scripting-xss-vulnerability) and, once a patched build above 3.5.50 is published, update the plugin immediately through the WordPress admin or WP-CLI and verify the installed version. If no fix is available, apply targeted compensating controls: stop granting Contributor (and Author) accounts to untrusted users and audit existing accounts with those roles, which directly removes the PR:L prerequisite but constrains editorial workflows that depend on external contributors; hold Contributor submissions in a pending state so a trusted user reviews raw content before it renders, accepting the added editorial latency; or, if the plugin is not essential to the site, deactivate and remove it entirely, which eliminates the attack surface at the cost of losing its Contact Form 7 field and layout functionality. Additional hardening that reduces - but does not eliminate - the risk includes a virtual-patching WAF rule blocking script payloads on the plugin's endpoints and a Content Security Policy that restricts inline and third-party script execution, though CSPs frequently break legitimate form and theme scripts and require testing. Note that generic 'defense in depth' guidance is insufficient here: the decisive controls are removing untrusted Contributor access and either updating past 3.5.50 or removing the plugin.
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 flaw is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a stored/Contributor-level cross-site scripting condition in the Themefic Ultimate Addons for Contact Form 7 WordPress plugin, tracked as CPE cpe:2.3:a:themefic:ultimate_addons_for_contact_form_7. The plugin extends Contact Form 7 with additional form fields and layout modules, and the vulnerable code path fails to escape or sanitize user-supplied input before rendering it back into a page. Because the input is persisted and later served to other users, the payload survives between request cycles, and because the CVSS vector carries S:C (scope changed), the injected script is treated as executing with privileges beyond the vulnerable component's original security scope, which is typical of stored XSS in a CMS plugin where the payload renders inside an administrative or editorial page. Contributor-level WordPress roles are intentionally able to submit content for review, so the injection point aligns with a permission that many multi-author sites hand out routinely; exploitation still hinges on a privileged user rendering the tainted output (UI:R), consistent with the independent assessment that this is a moderate-priority issue.
Know when Ultimate Addons 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:L/UI:R/S:C/C:L/I:L/A:L
Contributor auth (PR:L) and victim rendering (UI:R) are required; admin-context execution crosses privilege boundary (S:C) giving C:L/I:L, but XSS does not degrade availability (A:N).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Cross Site Scripting (XSS) in Ultimate Addons for Contact Form 7 <= 3.5.50 versions.
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.
A remote code execution vulnerability in all (CVSS 7.2). Risk factors: public PoC available. Vendor patch is available.
The Ultimate Addons for Contact Form 7 WordPress plugin before 3.1.29 does not sanitise and escape a parameter before ou
The Ultimate Addons for Contact Form 7 WordPress plugin before 3.1.29 does not sanitise and escape some of its settings,
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themefic Ultimate
The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Database m
PHP object injection in the Themefic Ultimate Addons for Contact Form 7 WordPress plugin (versions through 3.5.51) allow
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themefic Ultimate
Stored cross-site scripting in Ultimate Addons for Contact Form 7 through version 3.5.36 allows authenticated attackers
The Ultimate Addons for Contact Form 7 plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in ver
The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's U
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
EUVD-2026-85499
GHSA-cg2g-v3j4-jc6g
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB