Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level WordPress account
-
DeliveryInject script via slider 'data-href' parameter
-
ExploitPayload stored unsanitized in slider content
-
ExecutionAdmin/visitor loads injected page
-
PersistScript executes in victim browser 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 | Requires an authenticated account with contributor-level access or above on a WordPress site running Smart Slider 3 (nextendweb) version 3.5.1.38 or earlier; the attacker injects the payload through the 'data-href' parameter of a slider. Exploitation is limited by the need for valid contributor+ credentials (PR:L) - it is not exploitable by anonymous visitors. No end-user interaction is needed to plant the payload (UI:N), but the malicious script only fires when another user subsequently views the injected page, so impact depends on a victim loading that content. Realistic risk is highest on sites that allow open contributor registration or have many low-trust editorial accounts. |
| Impact | This is a moderate-severity, authenticated stored XSS with realistic but bounded risk. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N = 6.4) shows a network-reachable, low-complexity flaw, but PR:L means an attacker must already hold contributor-level (or higher) credentials on the WordPress site - this is the single biggest limiting factor. The scope change (S:C) reflects that injected script executes in the browser context of any user viewing the page, including higher-privileged admins, which is the classic privilege-escalation vector for contributor-tier XSS. Exploitation status: no public exploit identified at time of analysis - no POC, no CISA KEV entry, and no EPSS score was supplied, so there is no evidence of active or automated exploitation. No SSVC decision data was provided. The signals are internally consistent (Wordfence-classified stored XSS, changeset patch on plugins.trac.wordpress.org), so no vector/description conflict exists. Net: a real but not urgent priority - patch in normal cadence; it is not a high-CVSS-but-fake issue, yet the contributor-auth precondition keeps it well below a mass-exploitation threat. |
| Exploit ScenarioDerived | An attacker who has registered or acquired a contributor-level account on a Smart Slider 3-enabled WordPress site injects a malicious payload into the 'data-href' parameter of a slider, which is stored without sufficient sanitization. When an administrator or visitor later views the page containing the slider, the script executes in their session, enabling cookie/session theft or actions performed as the higher-privileged victim. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Stored cross-site scripting in the Smart Slider 3 WordPress plugin (Nextend, CPE nextendweb:smart_slider_3) up to and including version 3.5.1.38 lets an authenticated attacker with contributor-level access or higher inject arbitrary JavaScript through the slider's 'data-href' parameter, which is then rendered unsanitized on pages and executes in the browser of any user who views the injected content. Scoring is CVSS 3.1 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N); the attack requires valid contributor credentials and is therefore not reachable by anonymous visitors, but no victim interaction is needed to plant the payload - only a subsequent page view by another user to trigger it. There is no CISA KEV entry and no public exploit identified at time of analysis, though the risk is meaningfully elevated on sites with open contributor registration or many low-trust editorial accounts, where the stored script can be aimed at higher-privileged users or site visitors.
RemediationAI
Update Smart Slider 3 past the 3.5.1.38 boundary: the public fix is captured in the plugin Trac changeset 3654530 (https://plugins.trac.wordpress.org/changeset/3654530/smart-slider-3), but because the input provides only a source changeset rather than a confirmed tagged release version, treat this as upstream fix available (PR/commit); released patched version not independently confirmed - verify the plugin's changelog and install the first release published after 3.5.1.38 before assuming you are protected. Until the fixed build is deployed, mitigate by reducing the population that can reach the vulnerable sink: temporarily deactivate Smart Slider 3 (removes all sliders from the front end and any styling/layout that depends on them), or, if it must stay live, review and tighten roles so that untrusted accounts cannot hold contributor or higher (contributors can create the sliders/content that carry the payload) - this blocks the described PR:L path but will disrupt editorial workflows that depend on contributor submissions. Additionally, audit existing slider records for injected markup in 'data-href' values and remove any found (the payload is already persisted, so patching alone does not clean stored content), and deploy a WAF rule that rejects attribute-breaking sequences such as quote/Javascript-scheme payloads in slider parameters; note WAF coverage is signature-dependent and does not sanitize the stored data, so it complements rather than replaces the upgrade. Enforce httpOnly and SameSite cookie attributes and consider a Content-Security-Policy that disallows inline script to blunt the impact of any payload that survives - with the trade-off that strict CSP can break slider and other plugin scripts on the site.
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
Smart Slider 3 is a widely deployed WordPress slider/builder plugin published by Nextend; the CPE cpe:2.3:a:nextendweb:smart_slider_3:*:*:*:*:*:*:*:* matches all releases through 3.5.1.38. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting), specifically the stored variant: user-supplied content passed to the slider's 'data-href' attribute is neither sanitized on input nor escaped on output, so HTML/JavaScript context-breaking characters survive the round trip into the database and are re-emitted into the rendered page markup. Because WordPress stores the slider configuration and serves it to all front-end visitors (and to administrators previewing the slider in wp-admin), the injected script persists and executes in whatever authenticated or unauthenticated session loads that content, giving the attacker session-context actions such as cookie/session theft, credential harvesting via injected forms, CSRF-style privileged requests, or drive-by redirects. The CVSS scope change (S:C) reflects that the vulnerable component (the plugin/slider output) compromises resources beyond its own security authority - namely the surrounding WordPress origin and the browsing users' sessions. The 'data-href' element is a link target commonly wired to slider click behavior, making it a natural sink for an attribute-context payload.
Know when Smart Slider 3 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:N/S:C/C:L/I:L/A:N
Network-reachable stored XSS requiring contributor auth (PR:L); no user interaction to inject; scope change (S:C) as script runs in victims' context with limited C/I impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Smart Slider 3 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data-href' parameter in all versions up to, and including, 3.5.1.38 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Smart Slider 3
View allThe Smart Slider 3 WordPress plugin before 3.5.1.11 unserialises the content of an imported file, which could lead to PH
The Smart Slider 3 WordPress plugin before 3.5.1.14 does not properly validate and escape some of its shortcode attribut
Smart Slider 3 plugin for WordPress allows authenticated attackers with Subscriber-level privileges to read arbitrary fi
Stored Cross-Site Scripting in Smart Slider 3 (WordPress plugin by Nextend) versions up to and including 3.5.1.38 allows
Smart Slider 3 plugin for WordPress through version 3.5.1.33 allows authenticated attackers with Contributor-level acces
Directory traversal in the Smart Slider 3 WordPress plugin (all versions ≤ 3.5.1.36) exposes arbitrary server-side files
Deserialization of Untrusted Data vulnerability in Nextend Smart Slider 3.5.1.9. Rated medium severity (CVSS 4.3), this
Sensitive information exposure in the Smart Slider 3 WordPress plugin (all versions up to and including 3.5.1.37) allows
EUVD-2026-89667
GHSA-r2w8-9qw7-hrw6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB