# CVE-2026-92799: WordPress Bookly authorization bypass via type juggling

Source: https://junglewise.ai/threats/cve-2026-92799-the-online-scheduling-and-appointment-booking-system-bookly  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92799 · Severity: medium · CVSS 5.3 · Published 2026-09-25

The Bookly appointment scheduling plugin for WordPress allows unauthenticated attackers to bypass email and phone verification and modify customer account details including name, email, phone, and address. By submitting specially crafted data, attackers can redirect booking notifications to attacker-controlled email addresses, compromising customer communications and enabling account takeover or social engineering attacks.

Vendors: [Automattic](https://junglewise.ai/threats/vendors/automattic).

## Quick answers

**Is CVE-2026-92799 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92799 being exploited in the wild.

**How severe is CVE-2026-92799?** Medium severity, with a CVSS score of 5.3, published 25 September 2026.

**Which products and versions are affected?** Automattic Bookly up to and including 28.2.

**Is there a fix for CVE-2026-92799?** 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-92799 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-92799?** Check whether you run Automattic Bookly at an affected version. 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 stems from loose PHP type comparison (`!=`) in the `postValidateCustomer()` function when checking verification codes, combined with the booking AJAX controller registering all methods as unauthenticated CSRF-unprotected handlers. Attackers exploit this by submitting the JSON boolean `true` as the verification code, which passes the loose comparison against the session's integer code due to PHP's type juggling rules. An attacker with network access can perform customer record modifications without authentication or CSRF token validation.

## Affected products

- Automattic Bookly up to and including 28.2

## Timeline

- 2026-09-25: disclosed

## References

- [https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php](https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php)
- [https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php](https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php)