Online Scheduling and Appointment Booking System – Bookly
bookly-responsive-appointment-booking-tool · plugin
Known security vulnerabilities for Online Scheduling and Appointment Booking System – Bookly. Find out in seconds which version runs on your site with WP Lens.
32 known vulnerabilities
2 critical · 19 exploitable without logging in · 3 with public exploit code · latest Oct 10, 2026
Before you install
Use with care
- 17 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 28.7 · last updated Oct 26, 2026 · 60K+ installs
wordpress.org status checked on Nov 10, 2026
Vulnerabilities
- Critical 9.3
CVE-2026-61949unauthenticated≤ 27.7
WordPress Bookly plugin <= 27.7 - SQL Injection vulnerability
- Critical 9.1
CVE-2026-93399unauthenticated≤ 28.2
Online Scheduling and Appointment Booking System <= 28.2 - Insecure Direct Object Reference to Unauthenticated Arbitrary Booking Token Disclosure and Deletion v
- High 8.6
CVE-2026-13395unauthenticated→ 27.8
Bookly < 27.8 - Unauthenticated SQL Injection via staff_id
- High 7.7
CVE-2023-26526login required≤ 21.7.1
WordPress Bookly plugin <= 21.7.1 - Authenticated Arbitrary File Deletion vulnerability
- High 7.5
CVE-2026-96348unauthenticated≤ 28.2
WordPress Bookly plugin <= 28.2 - Broken Access Control vulnerability
- High 7.5
CVE-2026-89063unauthenticated≤ 28.1
Online Scheduling and Appointment Booking System <= 28.1 - Insecure Direct Object Reference to Unauthenticated Sensitive Data Access and Message Injection via '
- High 7.5
CVE-2026-14516unauthenticated≤ 27.5
Online Scheduling and Appointment Booking System <= 27.5 - Unauthenticated SQL Injection
- High 7.5
CVE-2026-42667unauthenticated≤ 27.4
WordPress Bookly plugin <= 27.4 - Sensitive Data Exposure vulnerability
- High 7.2
CVE-2026-13424unauthenticated≤ 27.7
Online Scheduling and Appointment Booking System <= 27.7 - Unauthenticated Stored Cross-Site Scripting via bookly_speed_up_update_addons AJAX action
- High 7.2
CVE-2026-5513unauthenticated≤ 27.2
Online Scheduling and Appointment Booking System – Bookly <= 27.2 - Unauthenticated Stored Cross-Site Scripting via 'bookly-customer-full-name' Cookie
- High 7.2
CVE-2026-12626high privilege≤ 28.2
Online Scheduling and Appointment Booking System <= 28.2 - Authenticated (Custom+) PHP Object Injection via 'value' Parameter
- High 7.2
CVE-2023-4691admin→ 22.4
Bookly < 22.4 - Admin+ SQLi
- High 7.1
CVE-2026-61944unauthenticated · needs a click≤ 27.7
WordPress Bookly plugin <= 27.7 - Cross Site Scripting (XSS) vulnerability
- High 7.1
CVE-2026-32540unauthenticated · needs a click≤ <= 26.7
WordPress Bookly plugin <= 26.7 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 6.8
CVE-2026-104898subscriber+≤ 28.4
Online Scheduling and Appointment Booking System <= 28.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Privilege Escalation via 'id' and 'wp
- Medium 6.5
CVE-2026-96347subscriber+≤ 28.2
WordPress Bookly plugin <= 28.2 - Insecure Direct Object References (IDOR) vulnerability
- Medium 6.4
CVE-2024-5584subscriber+≤ 23.2
WordPress Online Booking and Scheduling Plugin – Bookly <= 23.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Color Profile Parameter
- Medium 6.1
CVE-2023-1172unauthenticated
The Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the full name value in versions up to, and including, 21.5
- Medium 6.1
CVE-2018-6891unauthenticated · needs a click
Bookly #1 WordPress Booking Plugin Lite before 14.5 has XSS via a jQuery.ajax request to ng-payment_details_dialog.js.
- Medium 5.4
CVE-2026-2520subscriber+≤ 27.2
Online Scheduling and Appointment Booking System – Bookly <= 27.2 - Missing Authorization to Authenticated (Subscriber+) Limited Arbitrary Plugin Update
- Medium 5.4
CVE-2021-24930login required→ 20.3.1
Bookly < 20.3.1 - Staff Member Stored Cross-Site Scripting
- Medium 5.3
CVE-2026-103365unauthenticated≤ 28.4
Online Scheduling and Appointment Booking System <= 28.4 - Unauthenticated Sensitive Information Exposure in 'phone' Parameter to bookly_render_details
- Medium 5.3
CVE-2026-86838unauthenticated→ 28.3
Bookly < 28.3 - Unauthenticated Payment Bypass via Booking Price Manipulation
- Medium 5.3
CVE-2026-86837unauthenticated→ 28.3
Bookly < 28.3 - Unauthenticated Customer PII Update via Verification Bypass
- Medium 5.3
CVE-2026-92799unauthenticated≤ 28.2
Online Scheduling and Appointment Booking System <= 28.2 - Unauthenticated Authorization Bypass via PHP Type Juggling via 'verification_code' Parameter Type Jug
- Medium 5.3
CVE-2026-2519unauthenticated≤ 27.0
Online Scheduling and Appointment Booking System – Bookly <= 27.0 - Unauthenticated Price Manipulation via 'tips'
- Medium 4.8
CVE-2026-91847unauthenticated→ 28.2
Bookly < 28.2 - Unauthenticated AI Assistant Conversation Disclosure and Message Injection via IDOR
- Medium 4.8
CVE-2023-5209admin→ 22.5
Bookly < 22.5 - Admin+ Stored XSS
- Medium 4.8
CVE-2023-1159admin
The Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via service titles in versions up to, and including, 21.5 due t
- Medium 4.7
CVE-2026-86841admin→ 28.3
Bookly 23.2 - 28.2 - Bookly Administrator+ PHP Object Injection via Diagnostics Advanced Options
- Medium 4.3
CVE-2026-12905login required≤ 27.7
Online Scheduling and Appointment Booking System – Bookly <= 27.7 - Authenticated (Staff+) Insecure Direct Object Reference to Sensitive Information Exposure vi
- Low 3.8
CVE-2026-86839high privilege→ 28.3
Bookly < 28.3 - Staff+ Appointment and Payment Disclosure, Modification and Deletion via IDOR
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.