Quick answers
- Is CVE-2026-92619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92619 being exploited in the wild.
- How severe is CVE-2026-92619?
- High severity, with a CVSS score of 7.2, published 18 September 2026.
- Which products and versions are affected?
- Team Booking Booking Calendar up to 11.8.2.
- Is there a fix for CVE-2026-92619?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92619 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92619?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a privilege escalation flaw in the `handle_ajax_save()` function of the Booking Calendar plugin. The function fails to validate access controls for unregistered WordPress options, bypassing all `can_save`, `force_mode`, and `allowed_keys` checks when an attacker supplies an unregistered option name via the `wpbc_ajax_option_save` AJAX action. An authenticated attacker with Editor-level access or above can exploit this to modify core WordPress options such as `default_role` and `users_can_register`, then self-register a new Administrator account. Although a nonce check exists, it is ineffective because both the nonce value and action are attacker-controlled POST parameters, and a valid nonce can be trivially obtained via the `admin-ajax.php?action=rest-nonce` endpoint. The vulnerability affects all versions up to and including 11.8.2.
Affected products
- Team Booking Booking Calendar up to 11.8.2
Timeline
- 2026-09-18: disclosed