CVE-2026-49073: wpWax Directorist Booking SQL injection

CVE-2026-49073 · Severity: high · CVSS 8.5 · Published 2026-06-17

wpWax Directorist Booking is a WordPress plugin used to manage reservations and bookings on directory websites. A security flaw in this plugin allows an attacker with a basic user account to interact directly with the website's database. This could lead to the unauthorized theft of sensitive customer information or internal site data.

Vendors: wpWax.

Quick answers

Is CVE-2026-49073 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49073 being exploited in the wild.
How severe is CVE-2026-49073?
High severity, with a CVSS score of 8.5, published 17 June 2026.
Which products and versions are affected?
wpWax Directorist Booking up to 3.0.3.
Is there a fix for CVE-2026-49073?
A patch was published on 2026-06-08: Version 3.0.4 released to address the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49073 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-49073?
Check whether you run wpWax Directorist Booking at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A blind SQL injection vulnerability exists in the wpWax Directorist Booking plugin for WordPress due to improper neutralization of special elements in SQL commands. The flaw is present in versions up to and including 3.0.3. An attacker with at least 'Subscriber' level privileges can exploit this via network requests to perform unauthorized database queries. Successful exploitation allows for the extraction of sensitive data from the database, though it does not directly allow for data modification. The issue has been addressed in version 3.0.4.

Affected products

  • wpWax Directorist Booking up to 3.0.3

Timeline

  • 2026-05-26: other: Reported by researcher dutafi
  • 2026-06-08: advisory: Patchstack advisory published
  • 2026-06-17: disclosed: CVE published to NVD
  • 2026-06-08: patched: Version 3.0.4 released to address the vulnerability

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.