WP Directory Kit Plugin up to 1.5.4 on WordPress sql injection

Summaryinfo

A vulnerability was found in WP Directory Kit Plugin up to 1.5.4. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to sql injection. This vulnerability is traded as CVE-2026-16589. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in WP Directory Kit Plugin up to 1.5.4 and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The WP Directory Kit WordPress plugin before 1.5.5 does not sanitize and escape a parameter before using it in a SQL statement through one of its authenticated AJAX actions, which lacks authorization and nonce checks, allowing any authenticated user such as a Subscriber to perform SQL injection attacks.

The advisory is shared at wpscan.com. The identification of this vulnerability is CVE-2026-16589 since 07/22/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 1.5.5 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Name

• WP Directory Kit Plugin

Version

• 1.5.0
• 1.5.1
• 1.5.2
• 1.5.3
• 1.5.4

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion