# CVE-2026-9576: Fluent Booking < 2.1.2 - Calendar Manager+ Sensitive Information Disclosure via Attendee Export

> Calendar Manager users can access sensitive attendee PII from unowned calendar groups due to missing ownership verification in the export endpoint.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-fvjp-rchx-7wr5

## What is CVE-2026-9576?

CVE-2026-9576 is a medium-severity missing authorization vulnerability in Unknown Fluent Booking, published on 30 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Fluent Booking  WordPress plugin before 2.1.2 does not verify ownership of the requested group_id before exporting attendee data via the export endpoint, allowing users with at least the Calendar Manager role to retrieve attendees' PII (name, email, phone, address, payment information) from calendar groups they do not own.

## Which versions are affected by CVE-2026-9576?


## How do I fix CVE-2026-9576?

No fix has been published for CVE-2026-9576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9576 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9576 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9576 and fix it if it is affected.

What it is: CVE-2026-9576 is a medium-severity missing authorization vulnerability in Unknown Fluent Booking, published on 30 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9576 exists.

Affected product: Unknown Fluent Booking. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9576/ (Markdown: https://insights.sbomify.com/CVE-2026-9576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9576
- OSV: https://osv.dev/vulnerability/CVE-2026-9576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9576/
Summaries are generated and may contain mistakes; the official description above is the record.