Quick answers
- Is CVE-2026-61949 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61949 being exploited in the wild.
- How severe is CVE-2026-61949?
- Critical severity, with a CVSS score of 9.3, published 23 July 2026.
- Which products and versions are affected?
- Bookly <= 27.7.
- Is there a fix for CVE-2026-61949?
- A patch was published on 2026-07-23: Version 27.8 released to address the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61949 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61949?
- 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
An unauthenticated SQL injection vulnerability exists in the Bookly plugin for WordPress (versions 27.7 and below). The flaw is caused by improper neutralization of special elements used in an SQL command (CWE-89). A remote, unauthenticated attacker can exploit this by sending specially crafted network requests to the affected WordPress site. Successful exploitation allows the attacker to read sensitive data from the database, potentially leading to full site compromise. The issue is resolved in version 27.8.
Affected products
- Bookly Bookly <= 27.7
Timeline
- 2026-05-08: other: Reported by researcher dodoh4t
- 2026-07-16: advisory: Patchstack advisory published
- 2026-07-23: disclosed: CVE published to NVD
- 2026-07-23: patched: Version 27.8 released to address the vulnerability