# CVE-2026-18653: WP Directory Kit < 1.5.7 - Admin+ SQL Injection via section Parameter

> Administrators can exploit SQL injection in WP Directory Kit to read network-wide data on multisite installations, bypassing site-level access controls.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-36g7-7w4m-4xmc

## What is CVE-2026-18653?

CVE-2026-18653 is a high-severity SQL injection vulnerability in Unknown WP Directory Kit, published on 16 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP Directory Kit WordPress plugin before 1.5.7 does not sanitise and escape a parameter before using it in a SQL statement, allowing administrators to perform SQL injection attacks. On a multisite installation this lets an administrator of a single site read data belonging to the entire network, which they are not otherwise able to reach.

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

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


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

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

## Is CVE-2026-18653 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18653 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18653 is a high-severity SQL injection vulnerability in Unknown WP Directory Kit, published on 16 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18653 exists.

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-18653/ (Markdown: https://insights.sbomify.com/CVE-2026-18653/index.md)
```

## Sources

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

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