# CVE-2026-105195: Booking Calendar 10.15 - 11.8.2 - Editor+ Arbitrary Option Disclosure

> Editors can disclose arbitrary WordPress options, including core site configuration, due to inadequate access restrictions in the Booking Calendar plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-2c7f-rp38-5cq9

## What is CVE-2026-105195?

CVE-2026-105195 is a low-severity vulnerability in Unknown Booking Calendar, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Booking Calendar WordPress plugin before 11.8.3 does not adequately restrict which options a lower-privileged user can load through one of its settings handlers, allowing users with the Editor role and above to disclose the values of arbitrary WordPress options, including core site configuration.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-105195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105195 is a low-severity vulnerability in Unknown Booking Calendar, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105195 in the wild and no public exploit code.

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

## Sources

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

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