CVE-2026-96653
Deferred Deferred - Pending Action

SQL Injection in WP Directory Kit WordPress Plugin

Publication date: 2026-10-10

Last updated on: 2026-10-11

Assigner: Wordfence

Description
The WP Directory Kit plugin for WordPress is vulnerable to time-based SQL Injection via 'display_name' Profile Field (Second-Order) in all versions up to, and including, 1.5.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is a second-order injection: a Subscriber stores a display_name containing a single quote via their own profile, which WordPress preserves verbatim; the payload is then triggered when WdkCachedUserEditor::update_listings_user_editor() re-reads that stored value and passes it unsanitized to the SQL sink.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-10
Last Modified
2026-10-11
Generated
2026-10-19
AI Q&A
2026-10-10
EPSS Evaluated
2026-10-18
NVD
CVE-2026-96653
EUVD
EUVD-2026-96283

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wpdirectorykit WP Directory Kit 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

The WP Directory Kit plugin for WordPress has a time-based SQL Injection vulnerability in versions up to 1.5.9. An attacker with subscriber-level access can exploit this by storing a malicious display_name in their profile. When the plugin later processes this stored value unsafely in a SQL query, it allows the attacker to inject additional SQL commands to extract sensitive database information.

Detection Guidance

To detect this vulnerability, check for unauthorized SQL queries or unusual database activity. Inspect WordPress user profiles for display_name values containing SQL syntax like single quotes. Review logs for suspicious queries targeting the WP Directory Kit plugin.

Impact Analysis

If you use the WP Directory Kit plugin, an attacker could steal sensitive data from your WordPress database, such as user credentials, personal information, or other confidential data. This could lead to further attacks like unauthorized access or data breaches.

Compliance Impact

This vulnerability could lead to unauthorized access or exposure of personal data, violating GDPR and HIPAA requirements for data protection and security. Organizations using this plugin may face compliance violations, legal penalties, and reputational damage.

Mitigation Strategies

Update the WP Directory Kit plugin to the latest version. Remove any suspicious display_name values from user profiles. Implement input validation and output escaping for user-supplied data. Restrict subscriber-level access to sensitive functions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-96653. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart