# CVE-2026-16592: WP Directory Kit <= 1.5.7 - Contributor+ Non-Public Listing Field Disclosure via Shortcodes

> Contributors can disclose non-public listing content, including password-protected fields, via shortcodes in WP Directory Kit.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-jvcq-m5hf-56pc

## What is CVE-2026-16592?

CVE-2026-16592 is a low-severity missing authorization vulnerability in Unknown WP Directory Kit, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP Directory Kit WordPress plugin through 1.5.7 does not check authorization or listing visibility in one of its shortcodes, allowing users with a role as low as Contributor to disclose non-public listing content, including password-protected and hidden fields, belonging to other users.

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

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


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

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

## Is CVE-2026-16592 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16592 is a low-severity missing authorization vulnerability in Unknown WP Directory Kit, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16592 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-16592/ (Markdown: https://insights.sbomify.com/CVE-2026-16592/index.md)
```

## Sources

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

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