Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged user
-
DeliveryInject script into slider field
-
ExploitPayload stored unsanitized
-
ExecutionVictim views slider page
-
PersistScript executes in victim browser
-
ImpactHijack session or perform 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 account with at least low-level privileges sufficient to edit slider content in the Responsive Slider plugin (PR:L), and a victim must then view the page where the stored payload is rendered (UI:R) for the script to execute. Limiting factors: the attacker cannot act fully unauthenticated, the payload only triggers on victim page rendering rather than automatically, and impact is confined to browser-context script execution (Low C/I/A) rather than direct server compromise. The plugin must be installed and active on the target WordPress site, and the vulnerable slider output must be reachable by the targeted victim. |
| Impact | This is a stored (persistent) cross-site scripting flaw (CWE-79) in the 'Responsive Slider' WordPress plugin by Griden, affecting versions up to and including 0.1.9. The Patchstack-assigned CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, 6.5 Medium) indicates network-reachable, low-complexity exploitation that nonetheless REQUIRES low-privilege authentication (PR:L) to inject the payload and REQUIRES victim interaction (UI:R) for the stored script to fire, with a scope change (S:C) reflecting execution in the victim's browser outside the vulnerable component's security boundary. Impacts are rated Low across confidentiality, integrity, and availability, consistent with typical XSS consequences rather than full system compromise. No EPSS score, CISA KEV entry, SSVC decision, or public POC was supplied in the input, so there is no signal of active or imminent exploitation; the only tag is 'XSS'. On balance this is a genuine but modest-priority issue: the authentication-plus-interaction requirement and Low impacts place it well below critical, and the absence of any exploitation evidence combined with a niche plugin argues for routine rather than emergency patching. No conflicting signals were observed, though the lack of EPSS/KEV/POC data means real-world exploitation likelihood is simply unknown rather than confirmed low. |
| Exploit ScenarioDerived | A low-privileged authenticated user (e.g., a contributor or author able to configure the slider) injects a malicious script into a slider field that is stored and rendered without proper output encoding. When an administrator or other visitor subsequently views the page containing the slider, the stored script executes in their browser, potentially stealing session cookies or performing actions in their authenticated context. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Stored cross-site scripting in the Griden 'Responsive Slider' WordPress plugin (versions through 0.1.9) allows an authenticated user with at least low-level privileges to persist malicious JavaScript into slider content, which then executes in the browser of any visitor who renders the affected page. Because the payload is stored server-side and fires on victim page views, exploitation requires a victim to interact with the compromised slider (UI:R), while the attacker only needs rights sufficient to edit slider content (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, base 6.5). No public exploit code has been identified at time of analysis and the plugin is not reported as actively exploited (no CISA KEV listing); risk is elevated for multi-author or low-trust-administration WordPress sites where untrusted accounts can edit slider content.
RemediationAI
No vendor-released fix version is identified in the available data, so the primary action is to stop rendering unescaped stored slider content: deactivate and remove the Responsive Slider plugin (or update to a patched release if/when Griden publishes one - check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/responsive-slider/vulnerability/wordpress-responsive-slider-plugin-0-1-9-cross-site-scripting-xss-vulnerability?_s_id=cve for the fixed version before upgrading). Where the plugin must remain active, compensate by hardening the injection prerequisite: restrict the capability to create or edit slider content to fully trusted administrator accounts only, audit and purge any existing slider entries containing HTML/script, and disable the plugin's shortcode/widget output on public pages that untrusted authors can influence - noting that this narrows functionality and may break legitimate slider display. A web application firewall or content-security-policy ruleset scoped to the slider output can reduce execution of injected scripts but is bypassable and should be treated as defense in depth rather than a fix. Because exploitation requires an authenticated low-privileged account plus a victim page view, also review user roles and remove unnecessary author/editor accounts while remediation is pending.
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 an instance of CWE-79, improper neutralization of input during web page generation, in a WordPress plugin that manages image/content sliders. The plugin accepts slider configuration and content from users with editing capability and stores it in the WordPress database, but does not adequately escape or sanitize that stored data when later generating the front-end HTML page - the classic persistent (stored) XSS pattern. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L indicates network-reachable exploitation with low attack complexity, but it requires an authenticated actor holding low privileges (PR:L) plus a victim who views the page (UI:R). The scope change (S:C) reflects that the injected script executes in the context of the victim's browser session rather than within the vulnerable component itself, while impacts are limited to low confidentiality, integrity, and availability effects - script execution in the browser context rather than server compromise. The affected code sits in the WordPress plugin ecosystem (CPE/product: Responsive Slider), and the reported source is the Patchstack WordPress vulnerability database (audit@patchstack.com), consistent with a plugin-embedded content-rendering flaw.
Know when Wordpress Plugin 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
Stored XSS needs a low-privilege authenticated account to inject (PR:L) and victim rendering (UI:R); script runs cross-boundary in the browser (S:C) with Low C/I/A.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Griden Responsive Slider responsive-slider allows Stored XSS.This issue affects Responsive Slider: from n/a through 0.1.9.
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 Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-98298
GHSA-cmm6-9cwj-mxwq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB