Quick answers
- Is CVE-2026-18230 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18230 being exploited in the wild.
- How severe is CVE-2026-18230?
- High severity, with a CVSS score of 8.1, published 12 August 2026.
- Which products and versions are affected?
- WP Directory Kit before 1.5.6.
- Is there a fix for CVE-2026-18230?
- A patch was published on 2026-08-12: fixed in version 1.5.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18230 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-18230?
- 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 plugin does not sanitise or escape the "section" parameter before using it in an SQL statement within an authenticated AJAX action (wdk_admin_action). Although the endpoint requires WordPress authentication, it lacks proper role-based authorization checks, allowing any authenticated user (e.g., a Subscriber) to trigger SQL injection. The vulnerability can be exploited via blind time-based techniques to extract database values byte-by-byte. Attack preconditions: a logged-in user account with any role. The impact includes confidentiality breach (data extraction), integrity violation (database modification), and availability impact (SLEEP-based denial). The vulnerability was fixed in version 1.5.6 by enforcing administrator-only access.
Affected products
- WP Directory Kit WP Directory Kit before 1.5.6
Timeline
- 2026-08-10: disclosed
- 2026-08-12: patched: fixed in version 1.5.6