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

New CVE Detected

CVE-2026-14516 – Unauthenticated SQL Injection – Bookly WordPress Plugin ≤ 27.5

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

Summary

CVE-2026-14516 is a high-severity, unauthenticated time-based SQL Injection vulnerability in the Online Scheduling and Appointment Booking System – Bookly plugin for WordPress, affecting all versions up to and including 27.5. The flaw stems from insufficient escaping of user-supplied input and lack of proper SQL query preparation in the staff_ids parameter, enabling unauthenticated remote attackers to extract sensitive data from the underlying WordPress database. With a CVSS v3.1 base score of 7.5 (HIGH) and no authentication or user interaction required, all internet-exposed WordPress sites running a vulnerable version of Bookly are at immediate risk.

Technical details

  • Root cause: The staff_ids parameter is not properly escaped or sanitized before being incorporated into an existing SQL query, constituting CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).
  • Trigger conditions: Exploitation requires a deliberate two-request chain: (1) the attacker calls the unauthenticated AJAX action bookly_get_form_id to seed a booking session containing malicious staff_ids values; (2) the attacker subsequently triggers bookly_render_time, causing the tainted input array to reach the vulnerable SQL query.
  • No CSRF/nonce validation: Neither endpoint implements CSRF or nonce protection, meaning the two-request chain can be initiated entirely cross-site without any prior interaction with the target site.
  • Attack vector: Fully remote and unauthenticated — exploitable by any internet-connected attacker over standard HTTP(S) via WordPress’s wp-admin/admin-ajax.php endpoint with Bookly-specific AJAX actions.
  • Impact: Successful exploitation allows an attacker to append arbitrary SQL queries and exfiltrate sensitive information from the database, including user credentials, personally identifiable information (PII), booking records, and any other data stored in the WordPress database. There is no impact on integrity or availability.

Affected software

  • Online Scheduling and Appointment Booking System – Bookly (by ladela) — all versions up to and including 27.5

Severity

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

Mitigation and recommended actions

  • Immediate — Upgrade: Update the Bookly plugin to version 27.8 or later, which is the current available release in the WordPress Plugin Repository and addresses the vulnerability. Updates can be applied directly from the WordPress admin dashboard under Plugins > Available Updates.
  • If immediate patching is not possible: Consider temporarily disabling the Bookly plugin on internet-facing sites until the update can be applied. Additionally, where feasible, apply WAF rules to block or monitor unauthenticated POST requests to wp-admin/admin-ajax.php containing the bookly_get_form_id or bookly_render_time actions.

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge