Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged user
-
DeliveryInject script via vulnerable addon field
-
ExploitPayload stored in page content
-
ExecutionAdmin/user views affected page
-
ImpactScript executes 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 an authenticated WordPress account with at least low-level content-contribution privileges (PR:L, consistent with contributor/author-tier access that can submit content through the plugin's Elementor widgets), plus victim user interaction (UI:R) - a privileged user or site visitor must render the page containing the stored payload for the script to execute. Limiting factors: the attacker cannot be fully anonymous (some authenticated role is needed), the payload fires only when a victim views the affected content, and only sites running Premium Addons for Elementor at or below version 4.11.110 are affected. No non-default configuration is explicitly required by the available data, but the plugin must be installed and the vulnerable input field must be reachable by the attacker's role. |
| Impact | This is a moderate, authenticated stored XSS (CWE-79) in the Premium Addons for Elementor WordPress plugin, scored CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). The CVSS vector signals network reach with low complexity, but two factors meaningfully constrain real-world risk: PR:L means the attacker must already hold an authenticated, privilege-bearing account (typically contributor/author-level in WordPress plugin stored-XSS cases), and UI:R means a victim must view the injected page for the payload to fire. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the risk here is latent, not urgent. The scope change (S:C) and low C/I/A impacts are consistent with script execution in a victim's browser session rather than direct server compromise. Net assessment: a genuine but second-tier issue - not a high-real-risk, drop-everything flaw, but worth patching on a normal cadence given the plugin's broad deployment. Note that EPSS data is entirely absent (not zero), so exploitation probability could not be quantified; this is missing data, not a low-risk signal. |
| Exploit ScenarioDerived | An attacker with a low-privileged authenticated WordPress account (e.g. contributor or author) injects a malicious script payload through a Premium Addons for Elementor input field that is not properly sanitized, storing it in the site. When an administrator or another user later views the page or content containing the widget, the script executes in their browser session, potentially enabling session/cookie theft or actions in the victim's context. No public proof-of-concept is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Stored cross-site scripting in the Premium Addons for Elementor WordPress plugin (through version 4.11.110) lets an authenticated user with low-level content-contribution privileges plant persistent JavaScript inside Elementor-built pages or widgets, which then executes in the browser of any user who renders that content. The CVSS 6.5 score (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) reflects a network-reachable, low-complexity attack that requires an account with at least contributor/author-tier access and victim interaction, with the changed-scope (S:C) metric indicating the injected script acts in the context of the site origin rather than a confined component. Only sites running the plugin at or below 4.11.110 are affected, and no public exploit code or CISA KEV entry was identified at time of analysis.
RemediationAI
No vendor-released patch version is stated in the supplied data: the only reference is the Patchstack advisory, which lists 4.11.110 as the latest affected build and does not publish an explicit fixed version, so patch availability is not confirmed from available data - check the Patchstack entry and the plugin's WordPress.org changelog to confirm the first release after 4.11.110 and update to it. Until a fixed build is verified, apply targeted compensating controls: restrict or temporarily suspend contributor/author accounts that can create or edit Elementor content until trusted users are re-validated (trade-off: publishing workflow disruption); disable the specific Premium Addons widgets used to inject markup via Elementor's widget manager or, if the site does not rely on the plugin's widgets, deactivate the plugin entirely (trade-off: loss of page-builder functionality); deploy a WAF rule set that inspects POST bodies to admin-ajax.php, Elementor editor saves and post-save endpoints for script/event-handler patterns, and add a Content-Security-Policy that disallows inline script (trade-off: WAF false positives on legitimate rich-content editing and CSP breakage of inline scripts used by other plugins); and audit existing posts, widgets and postmeta for injected script tags or onerror/onload attributes and clean them, since stored payloads survive the upgrade. An administrator account should also be used to review and rotate any credentials or sessions that may have been exposed while a stored payload was live.
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
This is a CWE-79 improper neutralization of input during web page generation issue - specifically the stored (persistent) variant - in a WordPress plugin that extends the Elementor page builder. The plugin exposes widget and addon settings that are saved server-side (typically as post meta / serialized widget data) and later rendered into front-end HTML; the root cause is missing or insufficient sanitization on the way in and/or escaping on the way out, so HTML/script-bearing input submitted through those fields is persisted and re-emitted unescaped. The CPE record cpe:2.3:a:leapworx:premium_addons_for_elementor:*:*:*:*:*:*:*:* uses a wildcard version, meaning the CPE dictionary does not pin discrete versions and the affected range must be taken from the advisory text (everything through 4.11.110). The CVSS scope-change metric (S:C) is the key technical detail here: successful execution is not confined to the vulnerable plugin widget but occurs in the origin of the WordPress site itself, so injected script can reach cookies, session tokens, or admin-ajax endpoints belonging to the broader application. Because the payload is stored rather than reflected, it persists until the compromised post or widget data is cleaned.
Know when Premium Addons For Elementor 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
Authenticated low-privileged user can store the payload (PR:L), victim must view it (UI:R), and script runs cross-context in the browser (S:C) with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LeapWorx Premium Addons for Elementor premium-addons-for-elementor allows Stored XSS.This issue affects Premium Addons for Elementor: from n/a through 4.11.110.
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 Premium Addons For Elementor
View allUnauthenticated attackers can access private, draft, and pending template content in Premium Addons for Elementor WordPr
The Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Wrap
Stored cross-site scripting (XSS) in the LeapWorx Premium Addons for Elementor WordPress plugin, affecting versions thro
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Leap13 Premium Add
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Leap13 Premium Add
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Leap13 Premium Add
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Leap13 Premium Add
Stored cross-site scripting in Premium Addons for Elementor (versions through 4.11.110) allows an authenticated low-priv
Stored cross-site scripting in the Premium Addons for Elementor WordPress plugin (versions 4.11.105 and earlier) allows
Authenticated cross-site scripting in Premium Addons for Elementor, affecting versions up to and including 4.11.105, all
The Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Fanc
The Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the button onclic
EUVD-2026-97724
GHSA-x9ww-9fp7-2329
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB