CVE-2026-92619
HIGHDescription
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`.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-269 (Improper Privilege Management) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-12635 | Critical | 9.8 | 100% | - | Fix |
| CVE-2022-24637 | Critical | 9.8 | 99% | - | Fix |
| CVE-2017-5689 | Critical | 9.8 | 92% | KEV | Fix |
| CVE-2020-3243 | Critical | 9.8 | 88% | - | - |
| CVE-2024-21888 | High | 8.8 | 87% | - | - |
| CVE-2022-0441 | Critical | 9.8 | 85% | - | Fix |
Common questions
How do I fix CVE-2026-92619?
No published fix for CVE-2026-92619 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-92619?
CVE-2026-92619 has a CVSS v3 base score of 7.2, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-92619
Markdown
[](https://tridentstack.com/cve/CVE-2026-92619)HTML
<a href="https://tridentstack.com/cve/CVE-2026-92619"><img src="https://tridentstack.com/cve/badge/CVE-2026-92619.svg" alt="CVE-2026-92619"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-18.