# CVE-2026-92619: Booking Calendar <= 11.8.2 - Authenticated (Editor+) Privilege Escalation to 'data_name' Parameter

> Authenticated editors can escalate to administrator by manipulating unregistered WordPress options via the Booking Calendar plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-jrfx-j7fq-9588

## What is CVE-2026-92619?

CVE-2026-92619 is a high-severity vulnerability in wpdevelop Booking Calendar, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Booking Calendar plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 11.8.2 via the `wpbc_ajax_option_save` AJAX action. The vulnerability exists because the `handle_ajax_save()` function applies per-option safeguards only to names explicitly registered via `register_option_policy()`, causing `get_option_policy()` to return an empty policy — bypassing all can_save, force_mode, and allowed_keys checks — for any unregistered option name, including core WordPress options, while an attacker-controlled `data_name` parameter passes through `sanitize_key()` and is written directly to `update_option()` without restriction. This makes it possible for authenticated attackers with Editor-level access and above to escalate their privileges to Administrator by writing core WordPress options such as `default_role=administrator` and `users_can_register=1`, then self-registering a new Administrator account. The nonce check does not meaningfully restrict this attack, as both the nonce value and nonce action are attacker-supplied POST parameters, and a valid nonce is trivially obtainable via `admin-ajax.php?action=rest-nonce`.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-92619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92619 is a high-severity vulnerability in wpdevelop Booking Calendar, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92619 in the wild and no public exploit code.

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

## Sources

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

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