CVE-2026-18474: CWE-89 SQL Injection in WP Directory Kit
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.
AI Analysis
Technical Summary
The WP Directory Kit WordPress plugin versions prior to 1.5.6 contain a SQL injection vulnerability (CWE-89) due to improper sanitization and escaping of a parameter used in SQL queries. This allows unauthenticated attackers to inject malicious SQL code when a non-default search field type is configured, potentially compromising the database integrity or confidentiality.
Potential Impact
An attacker can exploit this vulnerability without authentication to execute arbitrary SQL commands on the backend database. This could lead to unauthorized data access, data modification, or other database-related impacts depending on the attacker's payload and database permissions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
CVE-2026-18474: CWE-89 SQL Injection in WP Directory Kit
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.
CVSS v3.1
Score 8.6high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WP Directory Kit WordPress plugin versions prior to 1.5.6 contain a SQL injection vulnerability (CWE-89) due to improper sanitization and escaping of a parameter used in SQL queries. This allows unauthenticated attackers to inject malicious SQL code when a non-default search field type is configured, potentially compromising the database integrity or confidentiality.
Potential Impact
An attacker can exploit this vulnerability without authentication to execute arbitrary SQL commands on the backend database. This could lead to unauthorized data access, data modification, or other database-related impacts depending on the attacker's payload and database permissions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WPScan
- Date Reserved
- 2026-07-31T09:35:37.902Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7c0ea3bf8831d539143520
Added to database: 08/12/2026, 06:11:47 UTC
Last enriched: 08/12/2026, 06:31:36 UTC
Last updated: 08/13/2026, 02:38:26 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.