The CVSS 9.1 score is technically accurate—unauthenticated SQL injection in a WordPress plugin warrants that rating—but it tells you little about what actually matters: the blast radius and the likelihood of recurrence. This plugin is a directory solution, which means the injection almost certainly targets custom database tables WordPress doesn't manage, sitting outside the sanitization patterns the plugin likely uses for core tables. The version boundary 'before 1.5.5' is narrow, which tells you the fix was surgical—a single parameter sanitization rather than a query architecture overhaul. That's the real signal. Surgical fixes in WordPress plugin CVEs have a documented pattern: they close the reported door while leaving adjacent code paths on the same custom tables vulnerable. If you patch this CVE, treat 1.5.5 as a starting point for your own audit, not an all-clear. Check the changelog—if it reads 'security hardening' without referencing broader code review, assume the underlying query architecture wasn't touched. More importantly: directory plugins are integration hubs. They touch email marketing, payment processing, geolocation APIs, and third-party sync workflows. The SQL injection reads whatever your database user can reach, not just directory listings. That means you're not containing a data leak—you're watching a potential pivot point. Review what credentials this plugin's database user has been granted. If it's broader than what's needed for directory functionality, that's your immediate remediation priority. Finally, watch for time-based blind injection. Directory plugins process high-volume search queries, so extraction traffic blends into normal usage patterns. An attacker running systematic extraction over hours isn't noise—they're just another heavy search user. Monitor for atypical query volumes from single IPs and for search operators or wildcards in search fields, which are the likely vectors for this injection.
CVE-2026-18473
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP Directory Kit WordPress plugin before 1.5.5 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUser input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.
General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.5.5 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WP Directory Kit in the plugin list
- Check the current version of the plugin
- If the installed version is before 1.5.5, click 'Update Now' to update to the latest version
- Alternatively, download version 1.5.5 or later from the WordPress plugin repository
- Upload and install the updated plugin files via Plugins > Add New > Upload Plugin
- Verify the update was successful by checking the plugin version after updating
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $5,750. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-18473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThe CVSS 9.1 score is technically accurate—unauthenticated SQL injection in a WordPress plugin warrants that rating—but it tells you little about what actually matters: the blast radius and the likelihood of recurrence. This plugin is a directory solution, which means the injection almost certainly targets custom database tables WordPress doesn't manage, sitting outside the sanitization patterns the plugin likely uses for core tables. The version boundary 'before 1.5.5' is narrow, which tells you the fix was surgical—a single parameter sanitization rather than a query architecture overhaul. That's the real signal. Surgical fixes in WordPress plugin CVEs have a documented pattern: they close the reported door while leaving adjacent code paths on the same custom tables vulnerable. If you patch this CVE, treat 1.5.5 as a starting point for your own audit, not an all-clear. Check the changelog—if it reads 'security hardening' without referencing broader code review, assume the underlying query architecture wasn't touched. More importantly: directory plugins are integration hubs. They touch email marketing, payment processing, geolocation APIs, and third-party sync workflows. The SQL injection reads whatever your database user can reach, not just directory listings. That means you're not containing a data leak—you're watching a potential pivot point. Review what credentials this plugin's database user has been granted. If it's broader than what's needed for directory functionality, that's your immediate remediation priority. Finally, watch for time-based blind injection. Directory plugins process high-volume search queries, so extraction traffic blends into normal usage patterns. An attacker running systematic extraction over hours isn't noise—they're just another heavy search user. Monitor for atypical query volumes from single IPs and for search operators or wildcards in search fields, which are the likely vectors for this injection.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-18473 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data