Skip to main content

Smart Slider 3 EUVDEUVD-2026-89667

| CVE-2026-14876 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-09-30 Wordfence GHSA-r2w8-9qw7-hrw6
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Obtain contributor-level WordPress account
  2. Delivery
    Inject script via slider 'data-href' parameter
  3. Exploit
    Payload stored unsanitized in slider content
  4. Execution
    Admin/visitor loads injected page
  5. Persist
    Script executes in victim browser session
  6. Impact
    Hijack 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.

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 – 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

Smart Slider 3 0 ≤3.5.1.38

Affected Packages

euvd smart_slider_3 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

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

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

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.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

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

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Medium
popular WordPress slider plugin with large but not universal install base
Data Quality
3 sources
Confidence: Low

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