Skip to main content

WP Directory Kit CVE-2026-18653

| EUVDEUVD-2026-59912 HIGH
SQL Injection (CWE-89)
2026-08-16 WPScan GHSA-36g7-7w4m-4xmc
7.2
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain or compromise WordPress site admin credentials
  2. Delivery
    Authenticate to WP Directory Kit admin interface
  3. Exploit
    Craft SQL injection payload in vulnerable parameter
  4. Execution
    Submit request to trigger unsanitized SQL execution
  5. Persist
    Query network-wide database tables beyond single-site scope
  6. Impact
    Exfiltrate cross-site user data, credentials, or PII

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

Exploitation requires a valid WordPress administrator account - either a network super admin or a single-site administrator. On a standard single-site WordPress installation, the attacker must already hold administrator-level credentials, and the incremental data access gained is limited since admins typically already have broad database visibility. The high-severity scenario is specific to WordPress multisite network deployments, where the shared database architecture enables cross-site data access. The WP Directory Kit plugin must be installed and activated on the target site. SSVC rates Automatable as 'no', meaning exploitation requires an authenticated session and cannot be scripted for mass targeting. Factors limiting exploitation: PR:H requires a compromised or malicious admin account; non-multisite installations face minimal incremental risk; UI:N means no victim interaction is needed once credentials are obtained.

Impact

The official CVSS 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) reflects high-privilege-required network exploitation with full C/I/A impact. In practice, risk is highly context-dependent. On a standard single-site WordPress installation, this is a privilege-abuse scenario: administrators already have broad database access, so the incremental attacker value is limited. On a WordPress multisite network, the risk escalates significantly - a malicious or compromised single-site admin can exfiltrate credentials, PII, or proprietary content from sibling sites they have no legitimate access to, representing a genuine authorization boundary violation. SSVC rates Technical Impact as 'total' and Automatable as 'no', confirming high damage potential if targeted but no mass exploitation pathway. EPSS at 0.17% aligns with SSVC's non-automatable rating. A public PoC from WPScan lowers the technical bar for a targeted attacker. Security teams should prioritize patching on multisite deployments over single-site installations.

Exploit ScenarioDerived

An attacker who has obtained or holds WordPress administrator credentials for a single site in a multisite network authenticates to the WP Directory Kit admin panel and submits a crafted request containing a SQL injection payload in the vulnerable parameter. The unsanitized input is executed against the shared network database, allowing the attacker to enumerate and dump tables from other sites on the network - extracting user credentials, email addresses, or other sensitive data that their site-admin role does not authorize them to access. A public PoC is available via WPScan, reducing the technical skill required for this step.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 17, 2026

SQL injection in WP Directory Kit WordPress plugin before 1.5.7 is exploitable by authenticated administrators, with materially elevated impact on WordPress multisite networks where a single-site admin can read data belonging to the entire network - data outside their authorized scope. A public PoC is available via WPScan, though EPSS sits at 0.17% (6th percentile), indicating targeted rather than opportunistic exploitation. No CISA KEV listing confirms active in-the-wild exploitation at time of analysis.

RemediationAI

Update WP Directory Kit to version 1.5.7 or later, which includes the vendor-released patch adding proper sanitization and escaping of the affected SQL parameter. The update is available through the standard WordPress plugin repository. Advisory details are at https://wpscan.com/vulnerability/e064c261-bc7b-4605-8da7-c7036fc396fc/. If immediate patching is not feasible on a multisite network, temporarily deactivate the WP Directory Kit plugin to eliminate the attack surface - this will disrupt directory-listing functionality but removes the SQL injection vector entirely. As an additional compensating control on multisite environments, restrict which users hold single-site administrator roles to only those with a genuine operational need, reducing the pool of principals who could exploit this flaw. Do not rely on WAF SQL injection filtering alone as the primary control, as admin-context requests may bypass signature-based rules.

Affected VersionsENISA

WP Directory Kit 0 <1.5.7

Affected Packages

euvd wp_directory_kit fix: 1.5.7

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

WP Directory Kit is a WordPress plugin for building directory listings (CPE: cpe:2.3:a:unknown:wp_directory_kit:*:*:*:*:*:*:*:*). The root cause is CWE-89 (Improper Neutralization of Special Elements in SQL Commands): a user-controlled parameter is passed unsanitized and unescaped directly into a SQL statement. The critical amplification factor is WordPress multisite architecture, where multiple sites share a single MySQL database instance. Because plugin code executing on one site operates against the same database connection used by all sites on the network, a SQL injection flaw allows a single-site administrator - whose application-layer access is scoped to their own site's tables - to query and read data from tables belonging to other sites in the network, bypassing the multisite authorization model entirely.

Know when Wp Directory Kit 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

Vendor (WPScan) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.6 HIGH

S:C reflects multisite authorization boundary crossing; I:L and A:N because demonstrated impact is cross-site data read, not confirmed destructive writes.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 17, 2026 - 21:22 NVD
7.2 (None) 7.2 (HIGH)
Patch available
Aug 16, 2026 - 07:01 EUVD
CVE Published
Aug 16, 2026 - 06:00 cve.org
HIGH 7.2
CVE Published
Aug 16, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The WP Directory Kit WordPress plugin before 1.5.7 does not sanitise and escape a parameter before using it in a SQL statement, allowing administrators to perform SQL injection attacks. On a multisite installation this lets an administrator of a single site read data belonging to the entire network, which they are not otherwise able to reach.

Executive ViewAI

Why It Matters

WordPress multisite networks running WP Directory Kit before version 1.5.7 face a data exposure risk where individual site administrators can access information beyond their authorization scope. The vulnerability is exploitable through a public proof-of-concept, necessitating immediate patching to protect sensitive cross-site data.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
common WordPress directory plugin, not universally deployed
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

56
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2024-3217 HIGH
8.8 Apr 05

The WP Directory Kit plugin for WordPress is vulnerable to SQL Injection via the 'attribute_value' and 'attribute_id' pa

CVE-2026-18474 HIGH POC
8.6 Aug 12

Unauthenticated SQL injection in WP Directory Kit WordPress plugin (all versions before 1.5.6) allows remote attackers t

CVE-2026-18230 HIGH POC
8.1 Aug 12

SQL injection in WP Directory Kit WordPress plugin (all versions before 1.5.6) allows any authenticated user - including

CVE-2025-13390 CRITICAL POC
10.0 Dec 03

The WP Directory Kit plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1

CVE-2023-2278 CRITICAL POC
9.8 Jun 13

The WP Directory Kit plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 1.1.9

CVE-2026-16589 HIGH POC
7.7 Aug 08

SQL injection via an unsecured AJAX endpoint in WP Directory Kit (WordPress plugin) before 1.5.5 allows any authenticate

CVE-2026-16594 HIGH POC
7.5 Aug 08

WP Directory Kit versions before 1.5.5 expose the plugin's full settings - including sensitive API keys and third-party

CVE-2026-16591 HIGH POC
7.2 Sep 26

Stored cross-site scripting in the WP Directory Kit WordPress plugin before version 1.5.8 lets an authenticated user who

CVE-2026-16593 MEDIUM POC
6.8 Sep 15

SQL injection in the WP Directory Kit WordPress plugin (versions through 1.5.7) lets authenticated users with page-build

CVE-2026-16590 MEDIUM POC
6.5 Aug 08

Unauthorized data exposure in the WP Directory Kit WordPress plugin (all versions before 1.5.5) allows any authenticated

CVE-2026-16595 MEDIUM POC
6.5 Aug 08

WP Directory Kit WordPress plugin before version 1.5.5 exposes sensitive site data to any authenticated user due to miss

CVE-2023-2351 MEDIUM POC
6.5 Jun 13

The WP Directory Kit plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a m

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy