CVE-2025-12388 MEDIUM

CVE-2025-12388: B Carousel Block – Responsive Image and Content Carousel <= 1.1.5 - Missing Authorization to Authenticated (Subscriber+) Server-Side Request Forgery

Vendor Bplugins
Product Carousel Block – Responsive Image and Content Carousel
Weakness CWE-918 · SSRF
Published November 5, 2025
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Carousel Block plugin for WordPress contains a server-side request forgery (SSRF) vulnerability that allows authenticated users to make the site send HTTP requests to internal or external systems on the attacker's behalf. An attacker with low-level access can exploit this to access internal services, retrieve sensitive data, or interact with systems behind the site's firewall. The vulnerability affects versions 1.1.5 and earlier.

What an attacker can do

03Attacker Capabilities

Make your site send HTTP requests to internal systems or external URLs to retrieve data or interact with services.

Potential impact on your site

04Site Impact

Internal services, APIs, or cloud metadata endpoints accessible from your server could be compromised or queried by an attacker with basic site access.

Conditions required to exploit

05Prerequisites

Attacker must have a low-level WordPress user account (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

November 5, 2025 CVE published
April 8, 2026 Record updated