CVE-2026-61949
Unauthenticated SQL injection in Bookly ≤27.7 enabling remote DB compromise.
Is CVE-2026-61949 being exploited?
Not confirmed. CVE-2026-61949 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-61949?
CVE-2026-61949 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-61949?
Not known from our data. No patch reference has been recorded for CVE-2026-61949, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-61949 affect?
CVE-2026-61949 affects Bookly WordPress plugin <=27.7, WordPress sites using Bookly. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61949?
Update Bookly to patched version; if unavailable, disable/remove plugin and audit DB.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQL injection allows remote attackers to read/modify/delete database, exfiltrate data, and potentially enable site takeover.
Immediate action required
- affected<= 27.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.