dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39531

CRITICAL · 9.3 CVSS v3.1 Published 2026-05-21
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.0.

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 the WP Directory Kit WordPress plugin. Attackers can inject malicious SQL queries through unsanitized input parameters, potentially allowing unauthorized database access, data exfiltration, or manipulation. The blind SQL injection variant means attackers infer information from application behavior differences rather than direct error output.

MitigationUpdate WP Directory Kit to the latest version if available, or implement parameterized queries and proper input sanitization in the plugin code to remediate the SQL injection vulnerability.

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. Check installed WP Directory Kit version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate WP Directory Kit, and record the version number shown
    Affected if Version displayed is 1.5.0 or lower
  2. Verify plugin is active
    In the WordPress plugins list, confirm WP Directory Kit status shows as Active
    Affected if Plugin is active and version is 1.5.0 or lower
  3. Identify vulnerable parameters
    Examine plugin source code files for GET/POST request parameters that handle user input, particularly in search, filter, or query functions
    Affected if User-supplied input parameters are processed without prepared statements or input sanitization
  4. Inspect database query handling
    Review plugin PHP files for direct SQL query construction using user input (such as $_GET, $_POST, or similar superglobals) concatenated into queries
    Affected if SQL queries directly incorporate unsanitized user input from request parameters

Your environment is affected if WP Directory Kit is installed, active, and running version 1.5.0 or lower with user input parameters that lack proper SQL sanitization.

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 version if available, or implement parameterized queries and proper input sanitization in the plugin code to remediate the SQL injection vulnerability.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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