Read the docs
TI-2026-70207 Aliases CVE-2026-96653GHSA-m2v9-gpjj-2h93

SQL injection in WP Directory Kit via stored display_name field

Priority LOW 28CWE-89Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
SQL injection
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-89.

Summary

The WP Directory Kit plugin for WordPress is affected in all versions up to and including 1.5.9. Insufficient escaping and an unprepared SQL query let a stored display_name value reach the database query unsanitized (CWE-89). An authenticated attacker with Subscriber access or higher can append SQL queries to existing ones and extract sensitive data from the database. The stored value is set in the attacker's own profile and triggers later, when the plugin re-reads it.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00242 15th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
wpdirectorykitWP Directory Kitup to 1.5.9—No fix listedCNA
  • WP Directory Kit Vendorwpdirectorykit Affected up to 1.5.9 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:wpdirectorykit:wp_directory_kit:*:*:*:*:*:*:*:*——wpdirectorykit
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:*:*:*:*:*:*:*:* Versions — — ·wpdirectorykit

Remediation

The sources list no fixed version for WP Directory Kit.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-96653
  2. 2026-10-10 Alias added: GHSA-m2v9-gpjj-2h93
  3. 2026-10-11 Priority changed: MEDIUM → LOW
  4. 2026-10-11 CISA SSVC decision points changed

References

Other 4

  • TI-2025-12241 WP Directory Kit <= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover CVSS 3.1CRITICAL 10.0
  • TI-2023-02136 WP Directory Kit <= 1.1.9 - Unauthenticated Local File Inclusion via wdk_public_action CVSS 3.1CRITICAL 9.8
  • TI-2026-30931 WordPress WP Directory Kit plugin <= 1.5.1 - SQL Injection vulnerability CVSS 3.1CRITICAL 9.3
  • TI-2026-28505 WordPress WP Directory Kit plugin <= 1.5.0 - SQL Injection vulnerability CVSS 3.1CRITICAL 9.3
  • TI-2026-22342 WordPress WP Directory Kit plugin <= 1.5.4 - SQL Injection vulnerability CVSS 3.1CRITICAL 9.3
  • TI-2024-03015 WP Directory Kit <= 1.3.0 - Authenticated (Subscriber+) SQL Injection CVSS 3.1HIGH 8.8
See all 29 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences