# CVE-2026-91025: Booking Manager < 2.1.21 - Subscriber+ Arbitrary User Plugin Meta Modification via IDOR

> Authenticated subscribers can modify arbitrary user settings, including administrators, due to missing authorization checks in the Booking Manager plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-f2f6-fww5-gh59

## What is CVE-2026-91025?

CVE-2026-91025 is a medium-severity missing authorization vulnerability in Unknown Booking Manager, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Booking Manager  WordPress plugin before 2.1.21 does not verify that a request to modify a user's Booking Manager  WordPress plugin before 2.1.21-specific settings targets the requesting user's own account, allowing any authenticated user with subscriber-level access and above to create or overwrite the Booking Manager  WordPress plugin before 2.1.21's per-user settings on arbitrary users, including administrators.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-91025 being exploited?

There is no known exploitation of CVE-2026-91025 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91025 is a medium-severity missing authorization vulnerability in Unknown Booking Manager, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-91025 in the wild and no public exploit code.

Affected product: Unknown Booking Manager. 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-91025/ (Markdown: https://insights.sbomify.com/CVE-2026-91025/index.md)
```

## Sources

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

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