dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-14383

HIGH · 7.5 CVSS v3.1 Published 2025-12-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Booking Calendar plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'dates_to_check' parameter in all versions up to, and including, 10.14.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Booking Calendar WordPress plugin (versions up to 10.14.8) contains a time-based blind SQL injection vulnerability in the 'dates_to_check' parameter. The flaw stems from insufficient input sanitization allowing unauthenticated attackers to inject arbitrary SQL queries, potentially exfiltrating sensitive data from the database.

MitigationUpdate the Booking Calendar plugin to version 10.14.9 or later. If immediate patching is not possible, consider restricting access to the affected endpoint via web application firewall rules while planning the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Booking Calendar plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name='booking-calendar'
    Affected if The Booking Calendar plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin, click on the Booking Calendar plugin to view its details and version number. Alternatively, check the plugin header in /wp-content/plugins/booking-calendar/booking-calendar.php or use: grep -i 'Version:' /wp-content/plugins/booking-calendar/booking-calendar.php
    Affected if The displayed version is 10.14.8 or lower
  3. Verify the vulnerable parameter is accessible
    The vulnerability exists in the 'dates_to_check' parameter. If you have access to web server logs or can test the endpoint, check for unauthenticated requests handling date validation. This is typically a public-facing booking functionality endpoint.
    Affected if The Booking Calendar date checking functionality is publicly accessible without authentication and accepts user-supplied input to the 'dates_to_check' parameter
  4. Review database logs for suspicious activity
    If database logging is enabled, review MySQL/MariaDB query logs for unusual time-based blind SQL injection patterns (e.g., BENCHMARK, SLEEP commands in queries originating from WordPress booking endpoints).
    Affected if Suspicious SQL injection attempts are found in database logs involving booking calendar queries

You are affected if the Booking Calendar plugin version is 10.14.8 or lower and the date checking functionality with the 'dates_to_check' parameter is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Booking Calendar plugin to version 10.14.9 or later. If immediate patching is not possible, consider restricting access to the affected endpoint via web application firewall rules while planning the update.

Recommended fix Moderate confidence

Booking Calendar version 10.14.9 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Booking Calendar plugin
  4. 4. If automatic updates are enabled, the plugin may update automatically; otherwise, click 'Update Now' if an update is available
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/booking and upload manually via Plugins > Add New > Upload Plugin
  6. 6. Verify the updated version number is 10.14.9 or higher
  7. 7. Test the booking functionality to ensure the plugin still works correctly after the update
Caveat Standard minor version updates typically do not include breaking changes; always test on a staging site first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14383 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data