Wp Directory KitWordPress extension · Wpdirectorykit
CVE-2024-37487
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in wpdirectorykit.Com WP Directory Kit allows Reflected XSS.This issue affects WP Directory Kit: from n/a through 1.3.5.
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 analysis · moderate confidenceReflected XSS vulnerability in WP Directory Kit plugin allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the web page. The vulnerability exists in versions up to 1.3.5, where the plugin fails to properly neutralize special characters in HTTP request parameters before displaying them in the generated HTML.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Directory KitWordPress extension
< 1.3.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check WP Directory Kit plugin versionIn WordPress admin, go to Plugins > Installed Plugins > WP Directory Kit and note the version number displayedAffected if Version shown is less than 1.3.6 (for example, 1.3.5 or earlier)
-
Confirm plugin is activeVerify that WP Directory Kit plugin status shows as Active, not deactivated or deletedAffected if Plugin is enabled on the site and version is below 1.3.6
-
Inspect plugin file handlingReview the plugin files for code that reads HTTP request parameters (such as $_GET, $_POST, or $_REQUEST) and outputs them directly into HTML without sanitization functions like esc_html() or esc_attr()Affected if The plugin processes and reflects URL parameters in web page output without proper encoding
-
Test parameter reflection manuallySubmit a harmless test string with special characters (such as <script>alert(1)</script>) as a URL parameter while visiting pages powered by the plugin, then inspect the page source to see if the string appears unescapedAffected if The test string appears raw in the HTML output rather than being escaped
You are affected if the installed WP Directory Kit version is below 1.3.6 AND the plugin is actively processing user input that gets reflected in generated web pages without sanitization.
Generated from the published advisory. Verify against your own configuration.
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.3.6
Apply vendor patch/upgrade to latest version of WP Directory Kit. If no patch available, implement output encoding on all user-supplied parameters before rendering in HTML, and add input validation layers.
1.3.6
- 1. Back up your WordPress site and database before making any changes
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- 3. Find WP Directory Kit in the plugins list
- 4. Click 'Update now' if an update is available, or manually update to version 1.3.6
- 5. After updating, verify the plugin version shows 1.3.6 or higher
- 6. Test that the affected functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Directory Kit
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37487 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37487 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
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
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