# CVE-2026-16589: WP Directory Kit < 1.5.5 - Subscriber+ SQL Injection via data_fields_list Parameter

> Authenticated users can execute SQL injection via the data_fields_list parameter in WP Directory Kit, allowing unauthorized database access.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-hf26-5fpg-7r9w

## What is CVE-2026-16589?

CVE-2026-16589 is a high-severity SQL injection vulnerability in Unknown WP Directory Kit, published on 8 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

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

## Which versions are affected by CVE-2026-16589?


## How do I fix CVE-2026-16589?

No fix has been published for CVE-2026-16589 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16589 being exploited?

There is no known exploitation of CVE-2026-16589 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16589 and fix it if it is affected.

What it is: CVE-2026-16589 is a high-severity SQL injection vulnerability in Unknown WP Directory Kit, published on 8 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16589 in the wild and no public exploit code.

Affected product: Unknown WP Directory Kit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16589/ (Markdown: https://insights.sbomify.com/CVE-2026-16589/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16589
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16589
- OSV: https://osv.dev/vulnerability/CVE-2026-16589

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16589/
Summaries are generated and may contain mistakes; the official description above is the record.