CVE-2025-13089
SQL Injection in WP Directory Kit Plugin Allows Data Exposure
Publication date: 2025-12-13
Last updated on: 2025-12-13
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | wp_directory_kit | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The WP Directory Kit plugin for WordPress has a SQL Injection vulnerability in the 'hide_fields' and 'attr_search' parameters in all versions up to 1.4.7. This occurs because user-supplied input is not properly escaped or prepared in SQL queries, allowing unauthenticated attackers to inject additional SQL commands to extract sensitive data from the database.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring for suspicious SQL injection attempts targeting the 'hide_fields' and 'attr_search' parameters in the WP Directory Kit plugin. Look for unusual HTTP requests containing SQL keywords or payloads in these parameters. Using tools like grep on web server logs to search for these parameters with suspicious content can help. For example, you can run commands such as: 1) grep -iE 'hide_fields=.*(union|select|drop|sleep|concat)' /path/to/access.log 2) grep -iE 'attr_search=.*(union|select|drop|sleep|concat)' /path/to/access.log Additionally, using web application firewalls (WAF) or intrusion detection systems (IDS) with SQL injection detection rules can help identify exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the WP Directory Kit plugin to version 1.4.8 or later, where the vulnerability has been fixed. The update includes nonce verification for AJAX requests, input sanitization and SQL escaping, access control enhancements, and filtering of dangerous SQL keywords. If updating immediately is not possible, consider disabling the plugin temporarily or restricting access to the affected parameters. Also, implement web application firewall rules to block SQL injection attempts targeting these parameters. [1]
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated attackers to extract sensitive information from your database by injecting malicious SQL queries. This can lead to data breaches and exposure of confidential information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to perform SQL injection attacks that can extract sensitive information from the database. This exposure of sensitive data could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information. Therefore, the vulnerability poses a risk to compliance by potentially enabling unauthorized access to protected data. [1]