Quick answers
- Is CVE-2026-16592 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16592 being exploited in the wild.
- How severe is CVE-2026-16592?
- Low severity, with a CVSS score of 2.7, published 15 September 2026.
- Which products and versions are affected?
- WP Directory Kit through 1.5.9.
- Is there a fix for CVE-2026-16592?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16592 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-16592?
- Check whether you run WP Directory Kit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in the wdk-listing-field-value shortcode that fails to verify whether the requesting user has permission to view specific listing fields or whether those fields should be visible. A Contributor-level user can craft a shortcode with a target listing ID (which are sequentially enumerable) and arbitrary field IDs to extract non-public content, including password-protected values and fields marked invisible on the frontend. The attack requires only contributor privileges and knowledge of a listing ID; the shortcode renders the sensitive data in draft post previews. No fix is currently available as of the advisory date (2026-09-23).
Affected products
- WP Directory Kit WP Directory Kit through 1.5.9
Timeline
- 2026-09-12: disclosed
- 2026-09-15: advisory