B Slider- Gutenberg Slider Block for WP <= 1.1.30 - Authenticated (Subscriber+) Missing Authorization to Arbitrary Plugin Installation
Strategic Overview
- Status
- Patched in 2.0.0
- Affected Plugin
- bSlider – Build Sliders That Bring Your Content to Life
- Affected Version
<= 1.1.30- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-8418
At a glance
CVE-2025-8418 is a high-severity Missing Authorization vulnerability in the bSlider WordPress plugin, affecting versions <= 1.1.30. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.0; sites on affected versions should update now. Disclosed August 2025, reported by wesley (wcraft).
Vulnerability Overview
The B Slider- Gutenberg Slider Block for WP plugin for WordPress is vulnerable to Arbitrary Plugin Installation in all versions up to, and including, 1.1.30. This is due to missing capability checks on the activated_plugin function. This makes it possible for authenticated attackers, with subscriber-level access and above, to install arbitrary plugins on the server which can make remote code execution possible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in bSlider <= 1.1.30 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For bSlider the fix is 2.0.0: builds <= 1.1.30 are affected, anything from 2.0.0 onward is not.
Remediation
Update to version 2.0.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: bSlider 2.0.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in bSlider – Build Sliders That Bring Your Content to Life
- 6.4CVE-2026-24383: B Slider <= 2.0.6 Stored Cross-Site Scripting
CVE-2026-24383 - 6.4CVE-2024-30432: B Slider - Slider for your block editor Stored XSS
CVE-2024-30432 - 4.3CVE-2025-8680: B Slider - Gutenberg Slider Block for WP <= 2.0.0 SSRF
CVE-2025-8680 - 4.3CVE-2025-8676: B Slider - Gutenberg Slider Block for WP Info Exposure
CVE-2025-8676 - 4.3CVE-2024-13514: B Slider- Gutenberg Slider… Private Post Disclosure
CVE-2024-13514
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C