Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege authenticated account
-
ExploitInject script into PowerPack widget field
-
ExecutionPayload stored and served to victim
-
ImpactScript executes in admin browser, session hijack
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 contributor/editor-level access to create or modify content using PowerPack Addons for Elementor widgets (PR:L), on sites running the plugin at version 3.1.0 or earlier. The stored payload only triggers when a victim user - typically an administrator or another content viewer - subsequently loads the page containing the injected input (UI:R), so exploitation is not fully automatic and depends on a second user viewing the malicious content. Limiting factors: attacker must already have a valid low-privilege account (no anonymous/unauthenticated path), the site must have the vulnerable plugin version installed, and the impactful cross-user compromise depends on a higher-privileged user viewing the affected page. |
| Impact | This is a moderate, real-but-not-urgent priority rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, base 6.5) shows network reach and low attack complexity, but two meaningful brakes: PR:L requires the attacker to already hold an authenticated, low-privilege account (typically a contributor/author who can edit PowerPack-driven Elementor content), and UI:R means a victim (usually an administrator or site visitor) must load the poisoned page for the payload to fire. The scope change (S:C) is the aggravating factor - injected script executes in the browser of other users, including higher-privileged admins, enabling classic session/account-takeover pivots, which is why confidentiality/integrity/availability each carry Low impact. No EPSS score, KEV listing, or public POC was provided in the input, so there is no signal of active exploitation or weaponized exploit code; the Patchstack sourcing indicates a researcher-reported, responsibly-disclosed flaw rather than an in-the-wild campaign. Net: a legitimate stored-XSS issue worth patching in normal cycles, but the authenticated-access prerequisite plus required user interaction keep real-world risk well below that of an unauthenticated RCE. No key signals conflict, though note EPSS/KEV/POC data were simply absent from the input, not confirmed negative. |
| Exploit ScenarioDerived | An attacker with a low-privileged authenticated account (e.g., a contributor who can build or edit Elementor content using PowerPack widgets) injects a malicious script payload into a vulnerable widget field, which is stored unsanitized. When an administrator or other user later views the affected page in the WordPress dashboard or on the front end, the script executes in their browser, potentially stealing session cookies or performing admin-level actions. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Stored cross-site scripting in the WordPress plugin PowerPack Addons for Elementor (slug powerpack-lite-for-elementor) through version 3.1.0 lets an authenticated attacker with contributor- or editor-level access inject malicious script through the plugin's Elementor widgets, which then executes in the browser of any user who later views the affected page. CVSS 3.1 scores this 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L), reflecting a low-privileged but authenticated requirement plus user interaction from the victim viewer, so exploitation is not fully automatic. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; the practical risk is a moderate, deliverable-but-conditional stored XSS rather than an emergency.
RemediationAI
No fixed version is identified in the provided data, so verify the current patched release against the vendor/Patchstack advisory at https://patchstack.com/database/wordpress/plugin/powerpack-lite-for-elementor/vulnerability/wordpress-powerpack-addons-for-elementor-plugin-3-1-0-cross-site-scripting-xss-vulnerability-2 and update the plugin as soon as a patched version is published; until then, the most effective control is reducing the population of users who can create or edit widget content with unescaped markup, since the root cause is a low-privileged authenticated author injecting stored script. Practically: audit contributor and editor accounts, remove the unfiltered_html capability from any non-administrator role (using a role editor, or the DISALLOW_UNFILTERED_HTML constant), and require editorial review before contributed content is published - the trade-off is a slower publishing workflow for legitimate authors. Disabling or unregistering the specific PowerPack widgets that accept rich markup removes the injection surface but degrades the plugin's page-building functionality. A WAF with stored-XSS rules can filter obvious payloads in POST bodies, though obfuscated payloads may bypass it and it does nothing for already-stored content, so previously submitted posts and their revisions should be reviewed and cleaned. Front-end and admin-side content security policy restrictions can limit script execution as a defence-in-depth measure, but may break Elementor rendering.
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 root cause is CWE-79, improper neutralization of input during web page generation, in a WordPress page-builder extension. PowerPack Addons adds widgets and content elements to Elementor; user-supplied values entered into those widgets are persisted (typically in post content or post meta) and later rendered into the page without adequate output escaping or input sanitization. Because the payload is stored rather than reflected, it survives across requests and is served to every subsequent visitor of the containing page or post. The CVSS scope-changed flag (S:C) captures that script executing in the victim's browser session can act beyond the vulnerable widget's own context, for instance reaching WordPress admin-surface content in the same origin. The CPE string cpe:2.3:a:ideabox_creations:powerpack_addons_for_elementor:*:*:*:*:*:*:*:* uses a wildcard, so the authoritative version boundary comes from the advisory: affected from n/a through 3.1.0.
Know when Powerpack 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-privilege contributor can inject stored script (PR:L), victim must view the page (UI:R), and cross-user execution crosses a scope boundary (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 IdeaBox Creations PowerPack Addons for Elementor powerpack-lite-for-elementor allows Stored XSS.This issue affects PowerPack Addons for Elementor: from n/a through 3.1.0.
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.
The “Elementor Addons - PowerPack Addons for Elementor” WordPress Plugin before 2.3.2 for WordPress has several widgets
The PowerPack Pro for Elementor plugin for WordPress is vulnerable to privilege escalation in all versions up to, and in
Cross-Site Request Forgery (CSRF) vulnerability in PowerPack Addons for Elementor PowerPack Pro for Elementor.10.8. Rate
A Stored Cross-Site Scripting (XSS) vulnerability exists in PowerPack Addons for Elementor (powerpack-lite-for-elementor
Stored cross-site scripting in PowerPack Addons for Elementor through version 3.1.0 allows authenticated users who can c
The PowerPack Addons for Elementor (Free Widgets, Extensions and Templates) plugin for WordPress is vulnerable to Stored
The PowerPack Addons for Elementor (Free Widgets, Extensions and Templates) plugin for WordPress is vulnerable to DOM-Ba
The PowerPack Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Twitter Twe
The PowerPack Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the settings of
The PowerPack Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the *_html_tag*
Vulnerability in IdeaBox Creations PowerPack Pro for Elementor.9.23. Rated medium severity (CVSS 6.1), this vulnerabilit
The PowerPack Addons for Elementor (Free Widgets, Extensions and Templates) plugin for WordPress is vulnerable to Stored
EUVD-2026-102867
GHSA-6w9f-v389-6m9g
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB