dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-22336

CRITICAL · 9.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Directorist Booking allows SQL Injection.This issue affects Directorist Booking: from n/a before 3.0.2.

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 · moderate confidence

A SQL Injection vulnerability exists in the Directorist Booking WordPress plugin. The vulnerability allows attackers to inject malicious SQL commands through unsanitized user inputs, potentially enabling unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpgrade Directorist Booking to version 3.0.2 or later to obtain the security patch. As a temporary measure, implement a WAF rule to block SQL injection attack patterns and ensure input validation is enforced at the application layer.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Directorist Booking plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Directorist Booking' in the plugin list.
    Affected if The plugin is not installed on the WordPress site.
  2. Check installed plugin version
    In the Plugins list, locate Directorist Booking and view the version number displayed below the plugin name. Compare this version to 3.0.2.
    Affected if The installed version is earlier than 3.0.2 (for example, 3.0.1, 3.0.0, or any version prior to 3.0.2).
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify that Directorist Booking shows as 'Active' rather than 'Inactive' or 'Draft'.
    Affected if The plugin is active and the version is prior to 3.0.2.
  4. Review application logs for SQL injection indicators
    Check web server access logs and WordPress debug logs for unusual query patterns, especially parameters containing SQL keywords (SELECT, UNION, INSERT, DROP) or special characters (' - ; ) submitted to booking-related URLs.
    Affected if Suspicious SQL-like strings appear in HTTP requests to the site.

The environment is affected if the Directorist Booking plugin is installed, active, and running a version earlier than 3.0.2.

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

Upgrade Directorist Booking to version 3.0.2 or later to obtain the security patch. As a temporary measure, implement a WAF rule to block SQL injection attack patterns and ensure input validation is enforced at the application layer.

Recommended fix Moderate confidence

Directorist Booking version 3.0.2

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate 'Directorist Booking' plugin in the list.
  4. 4. If an update to version 3.0.2 or later is available, click 'Update Now'.
  5. 5. Alternatively, you can download version 3.0.2 from the official WordPress plugin repository or Directorist website and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, clear any caching plugins and server-side caches.
  7. 7. Verify the plugin shows version 3.0.2 or later in the Plugins list.
  8. 8. Test critical booking workflows (create booking, edit booking, search bookings) to confirm functionality is intact.

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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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