CVE-2026-18474: WP Directory Kit · SQL Injection
Affects WP Directory KitSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 1.5.6 soon.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade WP Directory Kit to 1.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Directory Kit | Affected
| Fixed in
|
AI-suggested
Since the vulnerability affects versions before 1.5.6, upgrading to version 1.5.6 or later is recommended once the vendor confirms a fix. Until then, avoid configuring non-default search field types or restrict access to vulnerable plugin features as a temporary mitigation.
Description
The WP Directory Kit WordPress plugin before 1.5.6 does not sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated users when a non-default search field type is configured.