dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-32358

HIGH · 7.6 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in wpdevelop Booking Calendar booking allows Blind SQL Injection.This issue affects Booking Calendar: from n/a through <= 10.14.15.

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

A blind SQL injection vulnerability exists in the wpdevelop Booking Calendar WordPress plugin's booking functionality. Attackers can inject malicious SQL commands through improper neutralization of special elements, potentially allowing unauthorized data access or manipulation.

MitigationApply the vendor patch immediately upon release; until then, deploy WAF rules to detect and block SQL injection patterns in HTTP requests to the booking functionality.

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

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

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. Confirm Booking Calendar plugin is installed
    Navigate to WordPress admin > Plugins, or inspect /wp-content/plugins/ directory for 'booking' or 'wpdevelop' related folders
    Affected if The Booking Calendar plugin by wpdevelop is present on the WordPress site
  2. Identify installed plugin version
    Check the plugin header in main PHP file (e.g., read the 'Version:' field in the plugin file comments), or view the version in WordPress admin plugin list
    Affected if The installed version matches or falls within an affected version range (compare your version to the affected releases once published)
  3. Verify booking functionality is accessible
    Check if the booking calendar shortcode or widget is deployed on any published page or post; visit those pages to confirm booking forms load
    Affected if Public-facing booking forms or calendars are active on the site
  4. Inspect HTTP access logs for SQL injection attempts
    Review web server access logs (Apache/nginx) for requests to booking-related endpoints containing SQL metacharacters (e.g., ', UNION, SELECT, --, 1=1)
    Affected if Log entries show SQL injection patterns targeting booking parameters
  5. Check application error logs for SQL syntax errors
    Review PHP error logs or WordPress debug logs for SQL syntax error messages occurring around booking functionality
    Affected if Repeated SQL syntax errors appear in logs, indicating potential exploitation attempts

The environment is affected if the wpdevelop Booking Calendar plugin is installed with a vulnerable version and the booking functionality is publicly accessible, exposing the SQL injection entry point.

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

Apply the vendor patch immediately upon release; until then, deploy WAF rules to detect and block SQL injection patterns in HTTP requests to the booking functionality.

Recommended fix Moderate confidence

Latest available version of Booking Calendar (vendor should have released a version newer than 10.14.15 with the security fix)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Booking Calendar plugin (wpdevelop)
  4. 4. Check if an update is available and update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or the vendor's official website
  6. 6. Verify the update was successful and test booking functionality
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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