Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege WordPress user
-
DeliveryInject script into Prime Slider/Elementor field
-
ExploitPayload stored unsanitized
-
ExecutionAdmin views affected content
-
PersistScript executes in admin session
-
ImpactHijack session or escalate privileges
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 - consistent with a contributor/author-type role able to submit content through Prime Slider or its Elementor widgets), and it requires victim interaction (UI:R): a separate, typically higher-privileged user must render the page containing the stored payload for the script to fire. Limiting factors that reduce realistic risk: the attacker cannot act fully unauthenticated, the site must be running Prime Slider ≤ 4.7.1, and the impact depends on a privileged user actually viewing the injected content. It is not remote-unauthenticated against a default install. |
| Impact | This is a moderate-priority, not a drop-everything, issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, base 6.5 MEDIUM) describes a network-reachable but authenticated stored XSS that requires both low-privilege access (PR:L) and victim interaction (UI:R), with a scope change (S:C) reflecting that injected script executes in another user's browser context. No EPSS score was provided in the input, and there is no CISA KEV listing and no public proof-of-concept referenced, so there is no evidence of active exploitation or weaponization - the only intelligence source is a single Patchstack database entry. The real-world risk is therefore driven by likelihood of a malicious or compromised low-privilege WordPress user (e.g., contributor/author) rather than by opportunistic mass exploitation. Signals are internally consistent here: a MEDIUM CVSS, no KEV, and no POC all point to a genuine-but-lower-urgency vulnerability rather than a high-CVSS-but-low-real-risk mislabel or a quiet critical. Key missing data to note explicitly: EPSS probability is absent, POC status is unconfirmed (not stated either way), and the exact privilege level WordPress requires (contributor vs. author/editor) is not enumerated in the description - verify against the Patchstack advisory. |
| Exploit ScenarioDerived | An attacker holding a low-privilege authenticated WordPress account (such as contributor or author) on a site running Prime Slider ≤ 4.7.1 injects malicious JavaScript into a plugin-controlled field or Elementor widget input that is stored without proper neutralization. When a higher-privileged user - typically an administrator reviewing content in wp-admin - views the affected page, the stored script executes in their browser session. No public exploit code is identified at time of analysis, but stored XSS of this class is straightforward to craft given a valid account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Stored cross-site scripting (XSS) in the Prime Slider - Addons For Elementor WordPress plugin (bdthemes-prime-slider-lite) through version 4.7.1 lets an authenticated low-privileged user persist malicious script through slider/Elementor widget content, which then executes in the browser of any higher-privileged user who views the affected page (CVSS 6.5, AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). Because the payload is stored server-side and fires on page render, the practical impact is session/token theft, content injection, or privileged actions performed in the victim's context - though exploitation is not remote-unauthenticated and requires the victim to interact with the poisoned page. No public exploit code has been identified at time of analysis, and the issue is not confirmed actively exploited (no CISA KEV listing); this is a moderate-priority, not a drop-everything, issue.
RemediationAI
The provided intelligence does not specify a confirmed fixed version, so patch status is unconfirmed from available data - check the Patchstack advisory and the vendor's changelog for a release newer than 4.7.1 and upgrade immediately once one is published. Until then, the most effective controls target the PR:L precondition: audit WordPress accounts and remove or downgrade any contributor/author-level users who do not need slider or Elementor editing capability, since planting the payload requires an authenticated low-privileged account. If the plugin is not actively used, deactivate and delete it - this eliminates the attack surface entirely, at the cost of losing any live sliders (export widget settings first if they must be preserved). As a compensating layer, deploy a WAF or WordPress security plugin with XSS payload filtering on requests that write slider/widget content, understanding that signature-based filtering can be bypassed by encoding tricks. Finally, discourage administrators from browsing untrusted or user-submitted content while logged in, as the stored payload only fires on render (UI:R), and consider restricting admin session exposure to reduce credential/session theft impact.
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 affected component is a WordPress plugin, Prime Slider - Addons For Elementor, which adds slider and content widgets to the Elementor page builder (plugin slug bdthemes-prime-slider-lite; CPE cpe:2.3:a:bdthemes:prime_slider_-_addons_for_elementor). The flaw is rooted in CWE-79, Improper Neutralization of Input During Web Page Generation, in its stored (persistent) variant: user-supplied input is saved into the site's database without adequate output encoding or sanitization, and is subsequently emitted into HTML generated for slider/widget render. Stored XSS is more dangerous than reflected XSS because the payload is not tied to a single crafted link - it executes for every visitor who loads the affected page, including administrators and editors reviewing content. The CVSS vector's S:C (scope changed) reflects that the vulnerable component's handling of the payload allows impact to resources beyond its own security scope, i.e. the victim's browser session and the WordPress admin context. The PR:L and UI:R elements indicate a content-authoring account is sufficient to plant the payload, but a privileged victim must still render the page for execution to occur.
Know when Prime Slider 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 user can store the payload (PR:L), a victim must view it (UI:R), and script runs in another user's context (S:C) with limited C/I/A impact typical of XSS.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BdThemes Prime Slider - Addons For Elementor bdthemes-prime-slider-lite allows Stored XSS.This issue affects Prime Slider - Addons For Elementor: from n/a through 4.7.1.
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.
Stored cross-site scripting in the BdThemes Prime Slider plugin for WordPress (versions through 4.6.2) allows authentica
Stored Cross-Site Scripting in Prime Slider - Addons for Elementor plugin allows authenticated users with Author-level a
EUVD-2026-98360
GHSA-pwwj-rx47-x64x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB