Plugins · b-carousel-block · data as of 2026-11-04
Is Carousel Block safe? Known vulnerabilities and latest version
- Latest version
- 1.2.3
- Last updated
- 2026-08-30
- Active installs
- 7,000+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Create responsive image and content carousels in Gutenberg. Captions, autoplay, effects, navigation – build elegant sliders with no code. — by bPlugins
What to do
- Update to the latest version (1.2.3). Anything older than 1.1.6 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get b-carousel-block --field=version shows what you run; wp plugin update b-carousel-block updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.4 CVE-2025-12388 · published 2025-11-05
Server-side request forgery (SSRF) in Carousel Block (1.1.5 and older)
- Affected
- 1.1.5 and older
- Fixed in
- 1.1.6 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
Recent activity
- 2026-08-30 — latest release on wordpress.org (1.2.3).
- 2025-11-05 — Server-side request forgery (SSRF) disclosed (CVE-2025-12388), fixed in 1.1.6.
Get an email when Carousel Block has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Carousel Block (b-carousel-block) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by bPlugins (36 tracked)
Types found in this plugin: Server-side request forgery (SSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/b-carousel-block (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/b-carousel-block"><img src="https://laskyr.com/plugins/b-carousel-block/badge.svg" alt="Carousel Block vulnerability status"></a>