CVE-2026-92799 Auth bypass in Online Scheduling and Appointment Booking System – Bookly
Unauthenticated attackers can bypass verification checks to modify customer contact details in the Bookly WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-92799?
CVE-2026-92799 is a medium-severity authentication bypass vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Authorization Bypass via PHP Type Juggling in all versions up to, and including, 28.2. This is due to the `postValidateCustomer()` function using a loose PHP inequality operator (`!=`) to compare the session-stored one-time verification code against the attacker-supplied `verification_code` parameter — a flaw that is further exposed by the booking AJAX controller registering all its methods as `wp_ajax_nopriv_` handlers and unconditionally overriding `csrfTokenValid()` to return true, leaving the endpoint both unauthenticated and CSRF-unprotected. This makes it possible for unauthenticated attackers to bypass the phone/email ownership verification step and overwrite the name, email, phone, and address fields of any arbitrary existing Bookly customer record, redirecting that customer's booking notifications to attacker-controlled contact details. The bypass is achievable because the `json_data` input channel decodes input via `json_decode()`, which preserves real PHP types and causes the `wp_kses` filter to leave non-string values such as the JSON boolean `true` untouched; submitting `true` as the `verification_code` satisfies the loose comparison against the session's non-zero integer code (generated by `mt_rand(100000, 999999)`), causing `true != <non-zero int>` to evaluate as `false` and the guard to be bypassed.
Weakness: CWE-285
Which versions are affected by CVE-2026-92799?
How do I fix CVE-2026-92799?
No fix has been published for CVE-2026-92799 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-92799 being exploited?
There is no known exploitation of CVE-2026-92799 in the wild and no public exploit code.
Sources
Also known as GHSA-jv6x-x2jh-jfmr.