Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-61949 – Unauthenticated SQL Injection – Bookly WordPress Plugin ≤ 27.7

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-61949 is a critical unauthenticated SQL injection vulnerability affecting the Bookly appointment booking plugin for WordPress in all versions up to and including 27.7. The flaw allows any remote, unauthenticated attacker to interact directly with the underlying database, with a CVSS v3.1 base score of 9.3 (Critical). With over 60,000 active installations worldwide, the potential attack surface is substantial.

Technical details

  • Root cause: Insufficient sanitization and improper preparation of user-supplied input in the plugin’s database query logic, enabling injection of arbitrary SQL statements via unauthenticated HTTP requests.
  • Trigger conditions: No authentication, no privileges, and no user interaction are required. The attack can be executed entirely remotely over the internet.
  • Attack vector: Network-accessible; any unauthenticated HTTP request targeting an affected Bookly endpoint can deliver the malicious SQL payload.
  • Impact: High confidentiality impact — successful exploitation enables extraction of sensitive data from the WordPress database, including user credentials, personal information, booking records, and other stored data. Low availability impact is also present. The Changed scope (S:C) in the CVSS vector indicates the impact can extend beyond the plugin component itself to affect the broader WordPress environment.

Affected software

  • Bookly (Responsive Appointment Booking Tool) for WordPress — all versions ≤ 27.7

Severity

  • CVSS v3.1 Base Score: 9.3 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Mitigation and recommended actions

  • Immediate action: Update the Bookly plugin to version 27.8 or later, which contains the vendor-issued fix. Version 27.8 is available from the WordPress Plugin Repository.
  • If immediate patching is not possible: Restrict public access to the WordPress site or implement a Web Application Firewall (WAF) rule to filter and block malicious SQL injection payloads targeting Bookly endpoints until the update can be applied.
  • Administrators should also audit database logs for any anomalous or unexpected query activity that may indicate prior exploitation.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge