What the vulnerability does
01Description
The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to time-based SQL Injection via the 'staff_ids' parameter in all versions up to, and including, 27.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a two-request chain: an attacker first calls the unauthenticated bookly_get_form_id action to seed a booking session carrying malicious staff_ids values, then triggers bookly_render_time to cause the tainted array to reach the vulnerable query; CSRF/nonce validation is absent on both endpoints, meaning this chain can be initiated cross-site.
Explanation of Vulnerability in Simple Terms
02Summary
Bookly versions 27.5 and earlier contain a SQL injection vulnerability in the appointment booking system. An attacker can query the database directly without authentication to read sensitive information such as user details, appointment records, and payment data. No user interaction is required. Update to a version newer than 27.5 immediately.
What an attacker can do
03Attacker Capabilities
Read sensitive data from the site's database, including user information and appointment records.
Potential impact on your site
04Site Impact
Appointment data, user contact information, and potentially payment details could be exposed to unauthorized access.
Conditions required to exploit
05Prerequisites
Network access only; no authentication or user interaction required.
Key dates
06Disclosure timeline
July 28, 2026
CVE published
July 28, 2026
Record updated
