dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15289

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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, Appointment Booking System plugin for WordPress is vulnerable to time-based SQL Injection via the ‘wpdevart_id’ parameter in all versions up to, and including, 3.2.17 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. In order to exploit the vulnerability, the Pro version of the plugin must be installed and activated, with the 'Delete previous dates' option checked.

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 plugin fails to properly sanitize the 'wpdevart_id' parameter before using it in SQL queries, allowing unauthenticated attackers to inject time-based SQL queries. Exploitation requires the Pro version to be installed with the 'Delete previous dates' option enabled.

MitigationUpdate to version 3.2.18 or later which contains the fix; alternatively, disable the 'Delete previous dates' option until patching is possible.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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 Booking Calendar plugin installation
    Navigate to WordPress admin > Plugins and locate the Booking Calendar plugin. Note the installed version from the plugin list.
    Affected if Plugin is not installed or not the Pro version
  2. Confirm Pro version in use
    Access the Booking Calendar settings page or plugin header to verify it is the Pro version rather than the free version.
    Affected if The installed version is the free version only
  3. Locate Delete previous dates setting
    Go to Booking Calendar > Settings > General or Dates settings panel. Look for an option labeled 'Delete previous dates' or similar.
    Affected if The setting cannot be found or is not accessible (may indicate free version)
  4. Verify Delete previous dates is enabled
    Examine the checkbox or toggle for the 'Delete previous dates' option. Check if it is currently checked or set to enabled.
    Affected if The Delete previous dates option is enabled

User is affected if the Booking Calendar Pro version is installed with the Delete previous dates option enabled, allowing unauthenticated SQL injection via the wpdevart_id parameter.

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 to version 3.2.18 or later which contains the fix; alternatively, disable the 'Delete previous dates' option until patching is possible.

Recommended fix Moderate confidence

Plugin version 3.2.18 or latest available version (upgrade from 3.2.17 and earlier)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Booking calendar, Appointment Booking System' plugin
  4. Check if the Pro version is activated and the 'Delete previous dates' option is enabled in plugin settings
  5. Update the plugin to the latest available version (version 3.2.18 or later, as 3.2.17 and earlier are affected)
  6. Verify the update was successful by checking the plugin version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15289 — 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-2026-15289 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