Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious XSS payload link
-
DeliveryDeliver link to WordPress victim
-
ExploitVictim loads vulnerable Slider parameter
-
ExecutionScript executes in site context
-
ImpactHijack session or act as victim
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 attacker to deliver a crafted request/link to the vulnerable Slider by 10Web plugin (slider-wd) running version 1.2.63 or earlier on a WordPress site, and requires the victim to interact (UI:R) by loading that link in a browser. No authentication is needed (PR:N), so any unauthenticated attacker can originate the payload, but the dependency on victim interaction is the primary limiting factor - the flaw is not self-propagating and cannot be exploited without a human in the loop. The plugin must be installed and active for the vulnerable code path to be reachable. |
| Impact | CVSS 3.1 base score is 7.1 (High) with vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L - network-reachable, low complexity, no privileges required, but user interaction is mandatory and the impacts are only Low across confidentiality/integrity/availability with a scope change (typical of browser-context XSS). No EPSS score, KEV listing, or public POC is present in the supplied intelligence, so there is no evidence of active exploitation or automation; exploitation status is best characterized as no public exploit identified at time of analysis. The UI:R requirement means this is not a wormable, drive-by issue - it depends on luring a victim to load a crafted request/link - so despite the High CVSS this reads as a real-but-moderate priority rather than an emergency. The only source is a single Patchstack advisory; no independent 10Web vendor advisory or CISA corroboration was provided, so the version boundary (<= 1.2.63) and impact rest on Patchstack alone. |
| Exploit ScenarioDerived | An attacker crafts a malicious link or request targeting the vulnerable Slider by 10Web parameter and tricks a victim (site visitor or administrator) into loading it. Because no authentication is required (PR:N) but user interaction is (UI:R), the injected script executes in the victim's browser in the site's context, enabling session/cookie theft or actions performed as the victim. No public proof-of-concept is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated cross-site scripting in the Slider by 10Web WordPress plugin (slider-wd) affects all versions up to and including 1.2.63, allowing remote attackers to inject script that executes in a victim's browser session on the affected site. The CVSS 3.1 base score is 7.1 (High) with vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L - no privileges are required to originate the payload, but exploitation is not self-propagating: it depends on a human in the loop, since the victim must open an attacker-supplied request or crafted link (UI:R) for the script to run, and the vulnerable code path is only reachable while the plugin is installed and active. There is no public exploit code identified at time of analysis and the issue is not listed in CISA KEV, but the low attack complexity and unauthenticated attack surface make prompt patching or deactivation advisable for sites running the plugin.
RemediationAI
A vendor-released patched version is not independently confirmed from the available data, so the practical first step is to check the WordPress plugin repository and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/slider-wd/vulnerability/wordpress-slider-by-10web-plugin-1-2-63-cross-site-scripting-xss-vulnerability?_s_id=cve for a release newer than 1.2.63 and upgrade immediately once one exists, verifying in wp-admin that the installed version of slider-wd has advanced past the affected range. If no fixed release is available or the plugin is not essential, deactivate and remove Slider by 10Web entirely - this fully removes the attack surface, with the trade-off that any slider content embedded via its shortcodes will stop rendering on the site, so alternatives or static markup may need to be substituted first on staging. For sites that must keep the plugin running, apply virtual patching through a WAF or a WordPress security platform such as Patchstack's ruleset to block XSS payloads targeting the slider-wd endpoints, and treat this as an interim control only, since WAF signatures can be bypassed by encoding tricks and do not fix the underlying output-encoding defect. Additionally, deploy a Content Security Policy that disallows inline and untrusted script sources (noting it may break legitimate plugin scripts and requires testing), audit slider content and the plugin's database records for injected markup, and remind privileged users that because exploitation requires a victim to load an attacker-supplied link (UI:R), reducing click-through on untrusted links lowers - but does not eliminate - exposure. No public exploit code has been identified at time of analysis, but unauthenticated reachability with low attack complexity makes prompt remediation the priority.
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 issue is a CWE-79 improper neutralization of input during web page generation (cross-site scripting) in the WordPress plugin Slider by 10Web, identified in the plugin slug slider-wd and mapped in CPE as cpe:2.3:a:10web:slider_by_10web:*:*:*:*:*:*:*:*, i.e., an unversioned wildcard covering all releases of the plugin in the affected range rather than a single fixed build. WordPress plugin XSS of this class typically arises when user-controllable input handled by the plugin's shortcodes, AJAX handlers, or slider rendering routines is echoed into HTML without context-appropriate escaping or output encoding, so the injected markup is parsed as script by the browser rather than as inert text. The assessed vector reports a scope change (S:C), which is characteristic of browser-context script execution: the vulnerable component (the WordPress site hosting the plugin) is used as the origin for script that then acts on the victim's authenticated session and the site's same-origin data, which is why confidentiality and integrity impacts are rated Low but reach beyond the plugin itself. Because the vector carries PR:N, no authentication is needed to originate the payload, and AC:L indicates no special conditions or race window; the sole gating factor is UI:R, meaning a victim must browse to the crafted request for the XSS to fire. The plugin must be installed and active for the vulnerable code path to be reachable, and no exploitation in the wild or public proof-of-concept has been identified from the available intelligence.
Know when Slider By 10Web 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:N/UI:R/S:C/C:L/I:L/A:L
Unauthenticated network XSS (PR:N, AV:N) needs victim interaction (UI:R); browser execution crosses a trust boundary (S:C) with Low C/I and no realistic availability impact (A:N).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in Slider by 10Web <= 1.2.63 versions.
Executive ViewAI
The Slider by 10Web WordPress plugin (slider-wd) versions up to 1.2.63 is vulnerable to unauthenticated cross-site scripting, allowing attackers to inject malicious scripts into sites using the plugin. This affects any organization hosting WordPress sites with the vulnerable plugin, potentially leading to session hijacking, data theft, or site defacement. With no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, immediate mitigation is critical to protect users and brand reputation.
No vendor-released patch identified at time of analysis. Interim mitigations include deactivating the plugin, deploying WAF rules to block XSS attempts, enforcing Content Security Policy, and monitoring for suspicious activity.
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 Slider By 10Web
View allBlind SQL injection in the Slider by 10Web WordPress plugin through version 1.2.63 allows an authenticated high-privileg
Arbitrary file deletion via unauthenticated CSRF in the Slider by 10Web WordPress plugin (versions up to and including 1
EUVD-2026-96445
GHSA-w35c-qcgc-9wm2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB