dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-49073

HIGH · 8.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 wpWax Directorist Booking allows Blind SQL Injection. This issue affects Directorist Booking: from n/a through 3.0.3.

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

SQL injection vulnerability in wpWax Directorist Booking WordPress plugin allows blind SQL injection. The plugin fails to properly sanitize user input before using it in SQL queries, enabling attackers to inject malicious SQL commands. This is a high-severity (CVSS 8.5) issue affecting versions up to 3.0.3.

MitigationUpdate Directorist Booking to the latest version to patch the SQL injection vulnerability. If no update is available, disable the plugin until a patch is released, or manually audit and parameterize all database queries in the plugin code.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 version
    Log into WordPress admin, go to Plugins > Installed Plugins, locate Directorist Booking, and read the version number from the plugin description
    Affected if The displayed version is 3.0.3 or any version lower than 3.0.3
  2. Check plugin files for version string
    If admin access is unavailable, access the plugin directory via FTP or file manager, open the main plugin PHP file, and search for 'Version:' in the plugin header comment
    Affected if The Version field shows 3.0.3 or lower
  3. Identify if plugin is active
    In WordPress admin under Plugins, confirm whether Directorist Booking is currently activated
    Affected if The plugin is active and the version is 3.0.3 or below (inactive plugins with a vulnerable version are not exploitable but still at risk if activated)

A user is affected if the Directorist Booking plugin is installed, active, and the installed version is 3.0.3 or lower, since this version range contains the blind SQL injection vulnerability in unsanitized input handling.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Directorist Booking to the latest version to patch the SQL injection vulnerability. If no update is available, disable the plugin until a patch is released, or manually audit and parameterize all database queries in the plugin code.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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