WP Directory Kit < 1.5.7 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 1.5.7
- Affected Plugin
- WP Directory Kit
- Affected Version
< 1.5.7- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-18231
At a glance
CVE-2026-18231 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Directory Kit WordPress plugin, affecting versions < 1.5.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.5.7; sites on affected versions should update now. Disclosed August 2026, reported by Erwan LR.
Vulnerability Overview
The WP Directory Kit plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 1.5.7. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WP Directory Kit < 1.5.7 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP Directory Kit the fix is 1.5.7: builds < 1.5.7 are affected, anything from 1.5.7 onward is not.
Remediation
Update to version 1.5.7, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Directory Kit 1.5.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.3CVE-2025-13920: WP Directory Kit <= 1.4.9 Email Exposure
CVE-2025-13920 - 4.3CVE-2026-16594: Directory Kit Plugin Settings and API Key Disclosure
CVE-2026-16594 - 4.3CVE-2026-16595: Directory Kit Information Exposure
CVE-2026-16595 - 4.3CVE-2026-16590: Directory Kit Contact Message and User Data Disclosure
CVE-2026-16590
Other vulnerabilities in WP Directory Kit
- 10.0CVE-2025-13390: WP Directory Kit Authentication Bypass
CVE-2025-13390 - 9.8CVE-2023-2278: WP Directory Kit <= 1.1.9 Local File Inclusion
CVE-2023-2278 - 8.8CVE-2024-3217: WP Directory Kit <= 1.3.0 SQL Injection
CVE-2024-3217 - 7.5CVE-2026-28001: Directory Kit <= 1.5.4 SQL Injection
CVE-2026-28001 - 7.5CVE-2026-18474: Directory Kit <= 1.5.5 SQL Injection
CVE-2026-18474 - 7.5CVE-2026-18473: Directory Kit <= 1.5.4 SQL Injection
CVE-2026-18473 - 7.5CVE-2026-42672: WP Directory Kit <= 1.5.1 SQL Injection
CVE-2026-42672 - 7.5CVE-2026-39531: WP Directory Kit <= 1.5.0 SQL Injection
CVE-2026-39531
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C