dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13089

HIGH · 7.5 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The WP Directory Kit plugin for WordPress is vulnerable to SQL Injection via the 'hide_fields' and the 'attr_search' parameter in all versions up to, and including, 1.4.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

SQL injection vulnerability in WP Directory Kit plugin for WordPress via the 'hide_fields' and 'attr_search' parameters in versions up to 1.4.7. Unauthenticated attackers can inject arbitrary SQL queries due to insufficient escaping on user-supplied parameters and lack of prepared statements in the existing SQL query, allowing extraction of sensitive database information.

MitigationUpdate WP Directory Kit plugin to version 1.4.8 or later which contains the patch for this 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Verify WP Directory Kit plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Directory Kit' or check the plugin files in wp-content/plugins/wp-directory-kit/ for a version file
    Affected if Plugin is present on the WordPress site
  2. Check installed plugin version
    View the plugin main file header or the version number displayed in the WordPress plugins list
    Affected if Version is 1.4.7 or lower (versions 1.4.8 and later contain the fix)
  3. Identify if the plugin search/filter functionality is active
    Check if any directory pages with search or filtering features are published on the site; the vulnerable parameters are 'hide_fields' and 'attr_search' used in search queries
    Affected if Public-facing directory search or filter functionality exists and accepts these parameters
  4. Verify the vulnerable parameter exposure
    Test accessing a directory page with query parameters such as ?hide_fields=1 or ?attr_search=test to see if the application processes them without error or SQL validation
    Affected if The parameters are accepted and processed by the application without SQL injection protection

A site is affected if WP Directory Kit plugin version 1.4.7 or lower is installed and the directory search/filter functionality using 'hide_fields' or 'attr_search' parameters is publicly accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Directory Kit plugin to version 1.4.8 or later which contains the patch for this SQL injection vulnerability.

Recommended fix Moderate confidence

Version 1.4.8 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WP Directory Kit plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/wp-directory-kit/ and upload it manually
  6. 6. After updating, verify the plugin is running at version 1.4.8 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,590
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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