# CVE-2026-16590: WP Directory Kit < 1.5.5 - Subscriber+ Contact Message and User Data Disclosure

> Authenticated users can access other users' contact messages and data due to missing authorization checks in the WP Directory Kit plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 10 Aug 2026
- **Also known as:** GHSA-cgfm-pc65-3h3w

## What is CVE-2026-16590?

CVE-2026-16590 is a medium-severity missing authorization 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 perform authorization or nonce checks on one of its authenticated AJAX actions, allowing any authenticated user such as a Subscriber to retrieve stored contact messages and associated user data belonging to other users.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-16590 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16590 is a medium-severity missing authorization 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16590 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-16590/ (Markdown: https://insights.sbomify.com/CVE-2026-16590/index.md)
```

## Sources

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

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