Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Author-level account on target site
-
DeliveryUpload SVG with embedded JavaScript via Elementor upload route
-
ExploitStored payload awaits viewing
-
ExecutionVictim (e.g. admin) opens the SVG
-
ImpactScript runs in victim browser session
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 two specific preconditions: (1) the 'unfiltered file uploads' option within the Elementor Website Builder plugin settings must be explicitly enabled, which the description states is NOT the default; and (2) the attacker must already hold an Author role or higher on the WordPress site, giving upload access. The payload is stored, so it additionally depends on a second user (UI:R) opening or previewing the malicious SVG for the JavaScript to execute. These three factors - non-default configuration, authenticated mid-tier access, and required victim interaction - substantially limit real-world exploitability despite the network attack vector. |
| Impact | This is a moderate, conditional-risk issue rather than an urgent priority. The supplied CVSS 3.1 vector (AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H, 6.4) combines network reach with several strong dampeners: high attack complexity, high privileges, and required user interaction. The C:H/I:H/A:H impact rating appears inflated for a stored XSS (CWE-79) whose effect is JavaScript executing in a victim's browser - typical XSS impact is low/limited, so treat the 'High' triad with skepticism. Publicly available exploit code exists (WPScan), which raises practical concern, but there is no EPSS score provided and no CISA KEV listing, so there is no evidence of active exploitation - do not conflate POC availability with in-the-wild use. The single most important risk limiter is that exploitation requires the non-default 'unfiltered file uploads' setting to be enabled AND an attacker possessing Author-role-or-above access. Note a tension between signals: the CVSS vector marks PR:H, yet the description says 'Author role and above' (a mid-tier WordPress role), so the real privilege bar is likely lower than PR:H implies - verify role mapping with the vendor advisory. Net: a real but gated, lower-urgency vulnerability for most deployments, elevated only where the unsafe upload setting has been turned on. |
| Exploit ScenarioDerived | An attacker who already holds an Author (or higher) account on a WordPress site where the Elementor administrator has enabled unfiltered file uploads uploads a crafted SVG containing embedded JavaScript. When any other user - such as an administrator reviewing media - opens or previews that SVG, the script executes in their authenticated browser session, enabling session/cookie theft or admin-context actions. Public exploit code for this technique is available via WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Stored cross-site scripting in the Elementor Website Builder WordPress plugin before 4.3.5 allows users holding the Author role or higher to upload SVG files whose embedded JavaScript executes in the browser of anyone who later opens or previews the file. The vendor's CVSS vector marks this authenticated (PR:L), and exploitation carries two hard preconditions: the plugin's non-default 'unfiltered file uploads' setting must be enabled, and the attacker must already possess an Author-or-above account, with the payload only firing when a second victim interacts with the uploaded SVG. Publicly available exploit code exists (WPScan reference) but there is no evidence of active exploitation, so the practical risk is moderate and configuration-dependent rather than urgent.
RemediationAI
Vendor-released patch: Elementor Website Builder 4.3.5. Upgrading to 4.3.5 or later is the primary fix and should be applied through the WordPress plugin updater or a managed plugin deployment; verify the version after updating, since the CPE string carries no version granularity. If an immediate upgrade is not possible, disable the plugin's 'unfiltered file uploads' option - this removes the precondition entirely and, per the vendor, restores the default safe configuration, at the cost of blocking legitimate SVG uploads for content authors. As a supplementary control, review or temporarily restrict the Author role's upload privileges and audit the media library for SVG files that contain <script> tags or event-handler attributes, removing any found; note that role changes can disrupt contributor workflows. Where SVG support is genuinely required, restrict uploads to trusted roles or offload SVG handling to a sanitizing service, accepting the added operational complexity. Applying a content security policy that blocks inline script execution provides defense in depth against residual stored payloads but may break other site functionality and should be tested in staging first. Consult the WPScan advisory at https://wpscan.com/vulnerability/ba550282-d354-4d39-95c6-c4820a91f270/ for vendor-verified 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 flaw is a CWE-79 cross-site scripting variant rooted in inconsistent server-side sanitization of uploaded SVG content. SVG is an XML-based image format that supports <script> elements and event-handler attributes such as onload, so an SVG served from the site's own origin executes in that origin's security context if it is rendered inline rather than downloaded. Elementor's upload handling strips or validates SVG content on some routes but not all, leaving a bypass path in versions prior to 4.3.5. Because the malicious file is persisted in the WordPress media library, the payload is stored rather than reflected, and it fires whenever a victim - for example an editor or administrator reviewing media - opens the file directly or in a preview. WordPress's role model gates the upload behind the Author capability, and the plugin's 'unfiltered file uploads' option must be explicitly enabled, meaning a default installation is not exposed. The CPE records the affected package as an unversioned Elementor Website Builder entry, so version confirmation should be done through the WordPress plugin directory or the WPScan advisory rather than the CPE string alone.
Know when Elementor Website Builder 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:H/UI:R/S:U/C:H/I:H/A:H
Author-level upload is PR:L not PR:H; the required non-default 'unfiltered uploads' setting makes AC:H; stored XSS executes in another user's context (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Elementor Website Builder WordPress plugin before 4.3.5 does not sanitize uploaded SVG files on every upload route, allowing users with the Author role and above to upload a file containing JavaScript, which will run in the browser of any user who opens it. Exploitation requires unfiltered file uploads to be enabled in the Elementor Website Builder WordPress plugin before 4.3.5 settings, which is not the default.
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.
More in Elementor Website Builder
View allStored cross-site scripting in Elementor Website Builder for WordPress before 4.3.5 lets an authenticated user with the
Information disclosure in Elementor Website Builder (all versions before 4.1.4) allows authenticated WordPress users wit
Cross-site request forgery in Elementor Website Builder (all versions through 4.3.1) lets a remote attacker who holds no
Sensitive data exposure in Elementor Website Builder for WordPress (versions <= 4.1.3) allows contributor-level authenti
A DOM-based Cross-Site Scripting (XSS) vulnerability exists in Elementor Website Builder through version 3.35.5, allowin
Broken access control in Elementor Website Builder through version 3.35.5 permits high-privileged, network-based WordPre
EUVD-2026-107082
GHSA-cwqx-v6j9-jf65
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB