Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege WordPress user
-
DeliveryInject script into B Slider field
-
ExploitPayload stored in site
-
ExecutionAdmin views affected page
-
PersistScript executes in admin browser
-
ImpactSession hijack or privileged 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 WordPress account with sufficient privileges to submit or edit B Slider content (PR:L per the CVSS vector - plugin content-contribution capability such as contributor/author), and requires a victim with a browser session to view the rendered slider content (UI:R), typically a higher-privileged user or administrator for meaningful impact. The specific plugin field, parameter, or admin screen where the stored payload is injected and rendered is not described in the available sources. Limiting factors: exploitation is not fully unauthenticated, it depends on victim interaction, and impact is confined to the browser context of whoever views the malicious content; it only applies where the B Slider plugin (version ≤2.2.2) is installed and lower-privileged users can author slider content. |
| Impact | This is a stored cross-site scripting (CWE-79) flaw in the bPlugins 'B Slider' WordPress plugin with a reported CVSS 3.1 base score of 6.5 (vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). The vector signals network-reachable, low-complexity exploitation but requires some level of existing privilege (PR:L - i.e. authenticated per the vector) and victim interaction (UI:R), with a changed scope reflecting XSS execution in the victim's browser context and limited impact to confidentiality, integrity, and availability. The vuln.today decision label is 'this_month', indicating a moderate, non-emergency priority. No EPSS score was provided, there is no CISA KEV listing (so it is NOT confirmed actively exploited), and the single reference is a Patchstack advisory entry rather than verified working exploit code. On balance this is a real but routine stored-XSS issue typical of the WordPress plugin ecosystem - meaningful where the plugin is installed and lower-privileged users can submit content, but not an emergency; the lack of EPSS and the absence of any confirmed exploit mean widespread opportunistic exploitation is unproven. EPSS data is missing, which limits probabilistic assessment. |
| Exploit ScenarioDerived | A user with at least low-privilege authenticated access (e.g. contributor or author) injects a malicious script payload into a B Slider field that is stored and later rendered without proper neutralization. When a higher-privileged user such as an administrator views the page or admin screen where the slider content is displayed (UI:R), the script executes in their browser session, potentially enabling session/credential theft or admin-context actions. No confirmed working public exploit was identified at time of analysis; only a Patchstack advisory reference exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Stored cross-site scripting in the bPlugins 'B Slider' WordPress plugin (versions through 2.2.2) allows an authenticated low-privileged user to persist script payloads that execute in the browser of anyone who later views the rendered slider, carrying a CVSS 3.1 base score of 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). The flaw is only reachable where the plugin is installed and accounts with content-contribution privileges (contributor/author level) can submit or edit slider content, and the payload fires only when a victim with an active browser session loads the affected page - typically an administrator or editor, which is where the scope-changed impact becomes meaningful. No CISA KEV entry or public exploit code was identified at time of analysis; the vuln.today priority label is 'this_month' and the entry was reported through Patchstack.
RemediationAI
The supplied intelligence does not list an exact fixed plugin version; the affected range runs through 2.2.2, so consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/b-slider/vulnerability/wordpress-b-slider-plugin-2-2-2-cross-site-scripting-xss-vulnerability) for the vendor's current release and update the plugin as soon as one above 2.2.2 is published. Until an update is applied, the most direct compensating control follows from the exploitation preconditions: remove or restrict the ability of contributor/author-level accounts to submit or edit B Slider content (for example by revoking slider-editing capabilities from those roles or limiting slider authoring to administrators), with the trade-off that delegated content workflows will need to be rerouted through a trusted role. Where slider authoring cannot be restricted, consider deactivating the plugin entirely until it is patched - the trade-off being loss of the slider functionality on the site. Because the payload is stored, remediation should also include reviewing and removing any existing slider content that contains injected markup, since updating or restricting roles does not purge payloads already persisted in the database. Updating the plugin is the complete fix; the other measures reduce exposure but do not remove the underlying input-handling defect.
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
CWE-79 (Improper Neutralization of Input During Web Page Generation) in a WordPress plugin context means user-supplied slider content is stored in the database and later emitted into the page without adequate output encoding or sanitization, so markup and script survive the round trip and execute in the origin of the WordPress site. The CPE cpe:2.3:a:bplugins:b_slider:*:*:*:*:*:*:*:* and the ENISA EUVD entry (EUVD-2026-109731) both place the affected range at plugin versions from n/a through 2.2.2, i.e. the entire release history up to and including the current 2.2.2 build. Because the vector carries S:C (scope changed), the injected script can act outside the component that delivered it - in a WordPress deployment that means the attacker's script runs with the privileges of the viewing user in the site's own origin, potentially reaching administrative AJAX actions or nonce-protected UI. The vector's PR:L indicates the attacker must hold an authenticated account, and UI:R indicates the payload only triggers when a victim loads the affected page. Notably, the specific plugin field, parameter, shortcode attribute, or admin screen where the stored payload is injected and later rendered is not described in the available sources, and the trigger path should not be assumed.
Know when B Slider 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 content submission sets PR:L, stored payload needs a victim to load the page so UI:R, and XSS executing in the victim browser justifies the scope change S:C with limited 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 bPlugins B Slider b-slider allows Stored XSS.This issue affects B Slider: from n/a through 2.2.2.
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.
EUVD-2026-109731
GHSA-qr4j-rmw9-vv34
NVD
CVE.org
Vulnrichment
Exploit-DB