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.
CVE-2026-92799
Score 5.3 from GitHub Security Advisory published 2026-09-25. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 25, 2026
Last Modified
September 25, 2026
References (9)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php#L1447
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php#L15
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php#L785
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/frontend/modules/booking/Ajax.php#L903
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/lib/UserBookingData.php#L638
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/lib/Validator.php#L276
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.2/lib/base/Component.php#L182
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3707284%40bookly-responsive-appointment-booking-tool&new=3707284%40bookly-responsive-appointment-booking-tool
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/d24fa600-7698-4081-92f5-e11606928886?source=cve
Vendor Advisories for CVE-2026-92799(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 11:39 UTCEG score recompute
- 2026-09-25 11:39 UTCGHSA enrichment
- 2026-09-25 10:49 UTCEG score recompute
- 2026-09-25 10:49 UTCGHSA enrichment
- 2026-09-25 07:28 UTCEG score recompute
- 2026-09-25 07:02 UTCEG score recompute
- 2026-09-25 07:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-92799?
When was CVE-2026-92799 disclosed?
What is the CVSS score of CVE-2026-92799?
How do I remediate CVE-2026-92799?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92799
Is Your Infrastructure Affected by CVE-2026-92799?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.