Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify target WordPress site with Directorist Booking
-
DeliverySend crafted HTTP request with SQL injection payload
-
ExploitDatabase executes malicious query
-
ExecutionExtract sensitive data from WordPress database
-
ImpactOptionally execute resource exhaustion queries
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of Directorist Booking plugin versions prior to 3.0.2. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms the vulnerability is exploitable over the network with low attack complexity, requiring no authentication and no user interaction. Attackers need only identify WordPress sites running the vulnerable plugin version, which can be accomplished through automated scanning for plugin-specific file paths or HTTP headers. However, exploitation is limited to sites that have the Directorist Booking plugin actively installed and enabled, which narrows the attack surface compared to WordPress core vulnerabilities. |
| Impact | This vulnerability presents significant real-world risk despite no confirmed active exploitation. The CVSS base score of 9.3 (Critical) accurately reflects the attack surface: network-accessible, low complexity, no authentication or user interaction required. The Changed scope indicates database compromise could expose data from other WordPress plugins and core tables beyond Directorist Booking itself. However, several factors moderate immediate urgency: no CISA KEV listing indicates no widespread exploitation campaigns detected; EPSS data not available but unauthenticated SQLi vulnerabilities in WordPress plugins typically attract automated scanning within weeks of public disclosure; the Integrity impact is None (I:N), meaning attackers cannot modify database contents through this specific vector, limiting it to read-only data exfiltration and availability attacks. The Patchstack advisory publication creates a time-sensitive window where attackers may reverse-engineer the vulnerability from the advisory details even without a working proof-of-concept. Organizations running Directorist Booking must prioritize patching, as unauthenticated SQLi in web-facing applications represents one of the highest-priority vulnerability classes per SSVC framework: exploitable remotely, likely automatable for scanning, high technical impact to confidentiality. |
| Exploit ScenarioDerived | An unauthenticated remote attacker crafts a malicious HTTP request to a Directorist Booking endpoint, injecting SQL commands into a vulnerable parameter that lacks proper input sanitization. The injected SQL executes with the privileges of the WordPress database user, allowing the attacker to extract sensitive information such as user credentials, email addresses, booking records, and WordPress configuration secrets from the database. The attacker could also execute UNION-based or time-based blind SQL injection to enumerate database structure and exfiltrate data systematically, or craft resource-intensive queries to degrade site performance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 27, 2026
Unauthenticated SQL injection in Directorist Booking WordPress plugin allows remote attackers to extract sensitive database contents and cause limited denial of service. The vulnerability affects all versions prior to 3.0.2 and can be exploited remotely with low complexity and no authentication (CVSS:3.1 AV:N/AC:L/PR:N/UI:N). Patchstack has published details confirming the vulnerability exists in version 2.4.1 and earlier, with a vendor-released patch available in version 3.0.2. No CISA KEV listing or public exploit code identified at time of analysis.
RemediationAI
Upgrade Directorist Booking plugin to version 3.0.2 or later immediately via the WordPress admin dashboard (Plugins > Installed Plugins > Directorist Booking > Update Now) or by downloading from the official WordPress plugin repository. Version 3.0.2 contains vendor-released patches that properly sanitize SQL inputs per the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/directorist-booking/vulnerability/wordpress-directorist-booking-plugin-2-4-1-sql-injection-vulnerability?_s_id=cve. If immediate patching is not feasible, implement compensating controls with understanding of their limitations: disable the Directorist Booking plugin entirely until patched (eliminates attack surface but breaks booking functionality for site visitors), restrict WordPress admin access to trusted IP addresses only via .htaccess or firewall rules (does not prevent exploitation since vulnerability is unauthenticated and affects public-facing endpoints), deploy a Web Application Firewall with SQL injection signatures (may reduce automated exploitation but sophisticated attackers can bypass WAF filters, and creates false positive management overhead). Note that database-level permissions restrictions cannot mitigate this vulnerability since the WordPress database user requires read access for normal plugin operation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a classic SQL injection vulnerability (CWE-89) in the Directorist Booking plugin for WordPress. The affected software component is identified via CPE as directorist_booking:directorist_booking, a WordPress plugin that handles booking functionality for directory listings. SQL injection occurs when user-supplied input is improperly sanitized before being incorporated into SQL queries, allowing attackers to inject malicious SQL commands. The CVSS vector indicates a Changed scope (S:C), suggesting the vulnerability allows attackers to access resources beyond the plugin's normal security boundary, potentially affecting the entire WordPress database. The High confidentiality impact (C:H) combined with Low availability impact (A:L) suggests attackers can extract data and potentially cause database performance degradation or partial service disruption through resource-intensive queries.
Know when Directorist Booking gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
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.
Executive ViewAI
Directorist Booking WordPress plugin versions prior to 3.0.2 contain a critical unauthenticated SQL injection vulnerability (CVSS 9.3) that allows remote attackers to extract sensitive database contents without credentials. Any organization running this plugin on affected versions faces immediate risk of data breach and service disruption; this requires urgent patching across all WordPress instances using this plugin.
Vendor-released patch: version 3.0.2. If immediate patching is not feasible, disable the Directorist Booking plugin entirely and implement a Web Application Firewall (WAF) rule to block SQL injection patterns in requests to the plugin's endpoints; additionally, restrict plugin access to whitelisted IP addresses and enable WordPress database activity logging.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-25813
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB