CVE-2026-27538

WP Directory Kit <= 1.5.4 - Unauthenticated SQL Injection

2026-08-11 00:00
Taylsec

Strategic Overview

Status
Patched in 1.5.5
Affected Plugin
WP Directory Kit
Affected Version
<= 1.5.4
CVSS
5.9Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-27538
View all WP Directory Kit vulnerabilities

At a glance

CVE-2026-27538 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Directory Kit WordPress plugin, affecting versions <= 1.5.4. It carries a CVSS score of 5.9 (reachable over the network; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.5.5; sites on affected versions should update now. Disclosed August 2026, reported by Taylsec.

Vulnerability Overview

The WP Directory Kit plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 1.5.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WP Directory Kit <= 1.5.4 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP Directory Kit the fix is 1.5.5: builds <= 1.5.4 are affected, anything from 1.5.5 onward is not.

Remediation

Update to version 1.5.5, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Directory Kit 1.5.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C