Fluent Booking <= 2.1.1 - Authenticated (Calendar Manager+) Information Exposure
Strategic Overview
- Status
- Patched in 2.1.2
- Affected Plugin
- Fluent Booking – The Ultimate Appointments Scheduling, Events Booking, Events Calendar Solution
- Affected Version
<= 2.1.1- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-9576
At a glance
CVE-2026-9576 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Fluent Booking WordPress plugin, affecting versions <= 2.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Calendar Manager level or above. The issue is fixed in version 2.1.2; sites on affected versions should update now. Disclosed June 2026, reported by Md Amin Ullah Sheikh.
Vulnerability Overview
The Fluent Booking plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.1.1. This is due to missing per-booking access verification on the attendee export endpoint, which only checked for a broad Calendar Manager role rather than validating the requesting user's access to the specific booking group. This makes it possible for authenticated attackers, with calendar manager-level access and above, to export attendee booking data belonging to calendar groups they do not have permission to manage by supplying an arbitrary group_id parameter.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Fluent Booking <= 2.1.1 takes an account at Calendar Manager level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Fluent Booking the fix is 2.1.2: builds <= 2.1.1 are affected, anything from 2.1.2 onward is not.
Remediation
Update to version 2.1.2, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Fluent Booking 2.1.2 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Fluent Booking – The Ultimate Appointments Scheduling, Events Booking, Events Calendar Solution
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C