Radar sectionsDatabase
Check my site
WordPress plugin

WP Directory Kit <= 1.5.9 — Authenticated (Subscriber+) SQL Injection via 'display_name' Profile Field (Second-Order)

CVE-2026-96653Published · Updated

Action summary

Affected: ≤1.5.9Update to 1.6.0 or newer

All remediation steps
Severity
Medium6.5
CVSS
6.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:N Integrity
None
A:N Availability
None
Weakness
CWE-89 SQL Injection
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WP Directory Kit wpdirectorykit

  1. Affected≤ 1.5.9
  2. Patched in1.6.0

Update to 1.6.0 or newer.

You are affected if you run ≤ 1.5.9. Version 1.6.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP Directory Kit.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 1.6.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP Directory Kit to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Tarcísio Luchesi De Almeida Silva (Poystick).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP Directory Kit

All 43
More vulnerabilities in WP Directory Kit
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
<1.6.3Update to 1.6.3
CVE-2026-118418
Medium4.9Authenticated (Administrator+) SQL Injection
<1.6.3Update to 1.6.3
CVE-2026-118420
High7.5Unauthenticated SQL Injection via 'idfield' Parameter
≤1.6.0Update to 1.6.1
CVE-2026-109197
Medium6.5Authenticated (Custom+) SQL Injection via 'data_fields_list' Parameter
≤1.5.4Update to 1.5.5
CVE-2026-16596
Medium6.4Authenticated (Listing Admin+) Stored Cross-Site Scripting
≤1.5.7Update to 1.5.8
CVE-2026-16591

Same weakness (SQL Injection)

All SQL Injection
Other SQL Injection vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?