dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42672

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-01
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 Wp Directory Kit WP Directory Kit allows Blind SQL Injection. This issue affects WP Directory Kit: from n/a through 1.5.1.

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 blind SQL injection vulnerability exists in WP Directory Kit plugin. The vulnerability allows attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling data exfiltration or database compromise. Blind SQLi is particularly dangerous as it can extract data character-by-character even without direct error output.

MitigationUpdate WP Directory Kit to the latest patched version. If no patch is available, disable the plugin until a fix is released. Alternatively, implement input validation and parameterized queries at the application layer or WAF rules to block SQL injection payloads.

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. Confirm WP Directory Kit plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP Directory Kit' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Identify the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on 'WP Directory Kit' to view the plugin details, or check the plugin's main PHP file header for the 'Version' comment. Alternatively, examine the plugin folder metadata if you have file system access.
    Affected if A version number is displayed and can be compared to the fixed version.
  3. Compare version against fixed release
    Take the identified version number (e.g., from the plugin header or readme.txt file in the plugin directory) and compare it to version 1.5.2. Any version lower than 1.5.2 is considered vulnerable.
    Affected if The installed version is below 1.5.2.
  4. Verify public directory endpoint is accessible
    Check if the WP Directory Kit public-facing functionality is accessible by visiting common directory paths such as /directory/, /wplist/, or searching for any URLs containing 'wdk' or 'directory' on the site. These endpoints may process user input and could be vulnerable to SQL injection.
    Affected if The directory listing or search functionality is publicly accessible and processes user-supplied parameters.
  5. Review server logs for SQL injection patterns
    Examine web server access logs (Apache, Nginx, or equivalent) for requests to the WP Directory Kit endpoints containing common SQL injection payloads such as 'AND 1=1', 'AND 1=2', 'UNION SELECT', or time-based sleep commands like 'SLEEP()'. Use grep or log analysis tools to search for these patterns.
    Affected if Suspicious SQL injection payloads are found in the access logs targeting directory functionality.

The environment is affected if WP Directory Kit plugin is installed, the version is below 1.5.2, and the public directory functionality is accessible without additional access controls.

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 WP Directory Kit to the latest patched version. If no patch is available, disable the plugin until a fix is released. Alternatively, implement input validation and parameterized queries at the application layer or WAF rules to block SQL injection payloads.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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