Quick answers
- Is CVE-2026-13395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13395 being exploited in the wild.
- How severe is CVE-2026-13395?
- Informational severity, with a CVSS score of 8.6, published 30 July 2026.
- Which products and versions are affected?
- Bookly < 27.8.
- Is there a fix for CVE-2026-13395?
- A patch was published on 2026-07-13: Fixed in version 27.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13395 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-13395?
- Check whether you run Bookly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Bookly plugin for WordPress (versions prior to 27.8) contains a SQL injection vulnerability due to insufficient sanitization and improper casting of the 'staff_id' parameter within unauthenticated front-end booking requests. An attacker can exploit this by sending specially crafted network requests to the booking endpoint, allowing for the execution of arbitrary SQL commands. This can be leveraged to extract sensitive information from the database, such as user metadata and password hashes. The issue is fixed in version 27.8.
Affected products
- Bookly Bookly (Online Scheduling and Appointment Booking System) < 27.8
Timeline
- 2026-07-13: disclosed
- 2026-07-13: patched: Fixed in version 27.8
- 2026-07-30: advisory: NVD publication date