Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13090: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in listingthemes WP Directory Kit

0
Medium
VulnerabilityCVE-2025-13090cvecve-2025-13090cwe-89
Published: Tue Dec 02 2025 (12/02/2025, 11:20:06 UTC)
Source: CVE Database V5
Vendor/Project: listingthemes
Product: WP Directory Kit

Description

CVE-2025-13090 is a medium severity SQL Injection vulnerability in the WP Directory Kit WordPress plugin affecting all versions up to 1. 4. 6. It arises from improper neutralization of special elements in the 'search' parameter, allowing authenticated administrators to inject additional SQL queries. Exploitation requires administrator-level privileges and does not require user interaction. The vulnerability can lead to unauthorized disclosure of sensitive database information but does not impact data integrity or availability. No known exploits are currently in the wild. European organizations using this plugin should prioritize patching or mitigating this vulnerability to prevent potential data leaks. Countries with high WordPress usage and significant adoption of this plugin are most at risk. Mitigations include restricting admin access, implementing web application firewalls with SQLi detection, and monitoring database queries for anomalies.

AI-Powered Analysis

AILast updated: 12/02/2025, 11:58:17 UTC

Technical Analysis

CVE-2025-13090 is a SQL Injection vulnerability classified under CWE-89 found in the WP Directory Kit plugin for WordPress, affecting all versions up to and including 1.4.6. The vulnerability stems from insufficient escaping and lack of proper preparation of the 'search' parameter in SQL queries, which allows authenticated users with administrator privileges or higher to append malicious SQL commands to existing queries. This improper neutralization of special characters enables attackers to extract sensitive information from the backend database, such as user credentials, configuration data, or other confidential content stored within the WordPress environment. The vulnerability requires no user interaction but does require high-level privileges, limiting exploitation to insiders or compromised admin accounts. The CVSS v3.1 score is 4.9 (medium severity), reflecting network attack vector, low attack complexity, required privileges at the high level, no user interaction, and high impact on confidentiality but no impact on integrity or availability. There are currently no known exploits in the wild, and no official patches have been linked yet. The vulnerability was publicly disclosed on December 2, 2025, with the Wordfence team as the assigner. Given the widespread use of WordPress and the popularity of directory listing plugins, this vulnerability poses a risk to websites relying on WP Directory Kit for directory management and listings.

Potential Impact

For European organizations, the primary impact of CVE-2025-13090 is the potential unauthorized disclosure of sensitive data stored in WordPress databases. This can include personal data protected under GDPR, such as user information, contact details, or business-sensitive content. Exposure of such data could lead to regulatory penalties, reputational damage, and loss of customer trust. Since exploitation requires administrator-level access, the threat is particularly significant in environments where admin credentials are shared, weakly protected, or where insider threats exist. The vulnerability does not allow modification or deletion of data, nor does it cause denial of service, limiting the scope to confidentiality breaches. However, the ability to extract sensitive data can be leveraged for further attacks, such as privilege escalation or lateral movement within the network. European organizations with public-facing WordPress sites using this plugin are at risk, especially those in sectors handling sensitive personal or financial data. The lack of known exploits reduces immediate risk but should not lead to complacency given the ease of exploitation once admin access is obtained.

Mitigation Recommendations

1. Immediately restrict administrator access to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. 2. Monitor and audit administrator activities and database queries for unusual patterns that may indicate exploitation attempts. 3. Deploy a Web Application Firewall (WAF) with SQL Injection detection and prevention capabilities tailored to WordPress environments to block malicious payloads targeting the 'search' parameter. 4. Until an official patch is released, consider disabling or removing the WP Directory Kit plugin if it is not essential, or restrict its usage to non-administrative contexts where possible. 5. Implement principle of least privilege for WordPress roles to minimize the number of users with administrator-level access. 6. Regularly update WordPress core, plugins, and themes to incorporate security fixes promptly once available. 7. Conduct internal penetration testing focusing on SQL Injection vectors in WordPress plugins to identify similar vulnerabilities proactively. 8. Educate administrators about the risks of SQL Injection and the importance of secure coding and parameter handling in custom plugins or themes.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-12T20:07:21.330Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692ed0d35ae7112264bc9d96

Added to database: 12/2/2025, 11:43:15 AM

Last enriched: 12/2/2025, 11:58:17 AM

Last updated: 12/2/2025, 12:53:57 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats