# 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.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-jv6x-x2jh-jfmr

## 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 (Improper Authorization)

## 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.

## Is CVE-2026-92799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-92799 in the wild and no public exploit code.

Affected product: ladela Online Scheduling and Appointment Booking System – Bookly. 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-92799/ (Markdown: https://insights.sbomify.com/CVE-2026-92799/index.md)
```

## Sources

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

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