B Carousel Block – Responsive Image and Content Carousel <= 1.1.5 - Missing Authorization to Authenticated (Subscriber+) Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 1.1.6
- Affected Plugin
- Carousel Block – Showcase Images in Elegant Sliding Displays
- Affected Version
<= 1.1.5- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2025-12388
At a glance
CVE-2025-12388 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Carousel Block WordPress plugin, affecting versions <= 1.1.5. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.6; sites on affected versions should update now. Disclosed November 2025, reported by Sushi Com Abacate.
Vulnerability Overview
The B Carousel Block – Responsive Image and Content Carousel plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 1.1.5. This is due to the plugin not validating user-supplied URLs before passing them to the wp_remote_request() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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.
CWE-918: Server-Side Request Forgery (SSRF)
Carousel Block <= 1.1.5 carries this weakness at wp_remote_request(), and reaching it takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Carousel Block the fix is 1.1.6: builds <= 1.1.5 are affected, anything from 1.1.6 onward is not.
Remediation
Update to version 1.1.6, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Carousel Block 1.1.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C