Vulnerability in Online Scheduling and Appointment Booking System – Bookly (WordPress plugin) (CVE-2026-92799)
Summary
Vulnerability in Online Scheduling and Appointment Booking System – Bookly (WordPress plugin) (CVE-2026-92799). Risk of unauthorized operations or information disclosure. Exploitable via verification_code.
Original description
The description as published by the source.
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 != to evaluate as false and the guard to be bypassed.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-92799 has been found in Online Scheduling and Appointment Booking System – Bookly (WordPress plugin).
Attackers can target a specific entry point like verification_code over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Online Scheduling and Appointment Booking System – Bookly (WordPress plugin) CVE-2026-92799" on the vendor's site.
CVE-2026-92799 (Online Scheduling and Appointment Booking System – Bookly (WordPress plugin)) — CWE-285 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: verification_code / wp_ajax_nopriv_ / json_data / wp_kses
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in Online Scheduling and Appointment Booking System – Bookly (WordPress plugin). Attackers reach the vulnerable code path via verification_code without authentication.
Check the vendor advisory for the affected versions of Online Scheduling and Appointment Booking System – Bookly (WordPress plugin). Attack surface: verification_code / wp_ajax_nopriv_ / json_data / wp_kses.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Online Scheduling and Appointment Booking System – Bookly (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。