Skip to main content

Element Pack EUVDEUVD-2026-94249

| CVE-2026-105873 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-07 Patchstack GHSA-xrgm-256x-8gf7
6.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege WP account
  2. Delivery
    Inject script into Element Pack widget/page
  3. Exploit
    Payload stored unsanitized
  4. Execution
    Admin renders affected content
  5. Persist
    Script executes in victim browser session
  6. Impact
    Hijack session / perform admin actions

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 privileges (PR:L) capable of creating or editing content through Element Pack's Elementor widgets, and it requires a second user (UI:R) - typically an administrator or editor - to subsequently view the page containing the stored payload. The flaw is reachable over the network against the plugin's content-authoring surface, but it is NOT exploitable by fully unauthenticated attackers and will not fire without a victim rendering the malicious content. Limiting factors: the need for a pre-existing contributor/author-or-higher account sharply reduces exposure on single-admin sites, making multi-author installations (membership, editorial, or client-managed WordPress deployments) the realistic risk population.

Impact

This is a moderate, not top-tier, priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, base 6.5) describes a network-reachable but privilege-and-interaction-gated flaw: PR:L means the attacker must already hold an authenticated, low-privilege WordPress account (typically contributor/author able to use Elementor widgets), and UI:R means a victim (e.g., an administrator or other user) must render the poisoned content for the payload to fire. The scope change (S:C) is the one aggravating signal - the injected script executes in the victim's browser session rather than the plugin's own context, enabling session/credential theft or admin-action abuse, which is why impacts are rated Low across C/I/A rather than None. No EPSS score, KEV listing, or public POC was provided in the input, so there is no evidence of active exploitation or weaponization; the exploitation status is 'no public exploit identified at time of analysis.' The signals are internally consistent (authenticated stored XSS with user interaction), so there are no contradictions to flag - but note the input supplied no EPSS probability, meaning likelihood of widespread exploitation cannot be quantified from the data given. Overall: a real but second-tier issue, most dangerous on multi-author WordPress sites where lower-trust contributor accounts exist.

Exploit ScenarioDerived

An attacker with a low-privilege authenticated account (e.g., contributor or author) on a WordPress site running Element Pack crafts a page or widget containing a malicious script payload that the plugin stores without proper neutralization. When a higher-privileged user, such as an administrator reviewing or editing the content, loads the affected page in the WordPress dashboard or front end, the stored script executes in their browser session. No public exploit code was identified at time of analysis, but exploitation is straightforward given low attack complexity (AC:L).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Stored cross-site scripting in Element Pack Elementor Addons (bdthemes-element-pack-lite) through version 8.8.6 allows a low-privileged authenticated WordPress user to plant persistent script payloads inside Elementor widget content, which then execute in the browser of any higher-privileged user - typically an administrator or editor - who later renders the affected page. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, score 6.5) confirms that reachability is network-based but the attack requires a pre-existing contributor-or-higher account plus victim interaction, so single-admin sites are far less exposed than multi-author, editorial, or client-managed WordPress deployments. No public exploit code and no CISA KEV entry were identified at time of analysis, and this is assessed as a moderate, not top-tier, priority.

RemediationAI

No exact fixed version is identified in the provided data, so patch availability is not independently confirmed; the first action is to check the Patchstack advisory and the BdThemes plugin page for a release above 8.8.6 and update bdthemes-element-pack-lite to that version as soon as it is published. If no updated build is yet available, the highest-value compensating control is role reduction: audit and prune Contributor and Author accounts, since the attacker precondition is an authenticated low-privileged account, and multi-author sites should require editorial review of all widget-authored content before publication - the trade-off is added editorial overhead and reduced publishing velocity for legitimate contributors. Harden the WordPress role model by removing the unfiltered_html capability from non-Administrator roles and by denying Contributors the ability to publish directly, and consider a security plugin or WAF with outbound XSS filtering for Elementor widget content; be aware that aggressive HTML sanitization can strip legitimate widget markup and break page rendering, so test in staging. Because exploitation also requires victim interaction (UI:R), reducing the time administrators spend viewing unpublished or untrusted drafts and monitoring admin-area sessions for injected script is useful, but this is detection-oriented and not a substitute for upgrading once a patched release appears.

Affected VersionsENISA

Element Pack Elementor Addons 0 ≤8.8.6

Affected Packages

euvd element_pack_elementor_addons no fix

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 user-supplied input during web page generation, in its stored (persistent) variant. Element Pack Elementor Addons extends the Elementor page builder with additional widgets and modules; when content is created or edited through those widgets, user-controlled attribute values are persisted to the WordPress database and later emitted into HTML without adequate output encoding or sanitization. Because the payload is stored, it is served to every subsequent viewer of the page rather than only to the injecting user, and the CVSS scope-changed rating (S:C) reflects that code executes in the origin and privilege context of the victim - the WordPress admin area - rather than that of the low-privileged author who injected it. The affected CPE, cpe:2.3:a:bdthemes:element_pack_elementor_addons:*:*:*:*:*:*:*:*, uses a wildcard version, and the vendor advisory describes the impact range as all versions up to and including 8.8.6, i.e., the free/lite plugin slug bdthemes-element-pack-lite. The precondition profile (PR:L plus UI:R) means this is a privilege-escalation-adjacent content injection issue, not an unauthenticated remote compromise of the underlying web server.

Know when Element Pack Elementor Addons 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

Vendor (Patchstack) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 6.5 MEDIUM

Authenticated low-privilege content author injects the payload (PR:L), a victim must render it (UI:R), and the script runs in the victim's browser context (S:C) with limited C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BdThemes Element Pack Elementor Addons bdthemes-element-pack-lite allows Stored XSS.This issue affects Element Pack Elementor Addons: from n/a through 8.8.6.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Medium
popular WordPress Elementor addon, widely installed but not ubiquitous
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy