dbcve.org
Wp Directory KitWordPress extension · Wpdirectorykit

CVE-2024-29774

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WpDirectoryKit WP Directory Kit allows Reflected XSS.This issue affects WP Directory Kit: from n/a through 1.2.9.

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 confidence

A reflected cross-site scripting (XSS) vulnerability exists in WP Directory Kit versions up to 1.2.9. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected back in the web page without proper output encoding. This occurs during web page generation when the plugin processes and displays user-supplied data.

MitigationUpdate WP Directory Kit to the latest version once available, as vendor patches for XSS typically address input validation and output encoding. If no update is available, consider disabling the plugin until a fix is released, or implement web application firewall rules to block malicious parameter patterns.

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
Affected:< 1.3.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed WP Directory Kit version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, locate WP Directory Kit, and note the version number displayed. Alternatively, open wp-content/plugins/wpdirectorykit/readme.txt and locate the Version field in the file header.
    Affected if The version is 1.2.9 or lower (any version below 1.3.0)
  2. Confirm plugin is active
    Verify the WP Directory Kit plugin is currently activated on the WordPress site. Check the plugins list status column in WordPress admin.
    Affected if The plugin is active and running
  3. Identify user input handling
    Review any public-facing forms, search fields, or submission pages created by WP Directory Kit (e.g., directory submission forms, search widgets, listing details). These are the points where user-supplied data enters the application.
    Affected if The plugin accepts and displays user input on the site, as reflected XSS triggers when unsanitized input is reflected back in the page output

The site is affected if WP Directory Kit version is below 1.3.0 and the plugin is actively handling user input on public pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.0 or later
Fixed in 1.3.0
Interim mitigation

Update WP Directory Kit to the latest version once available, as vendor patches for XSS typically address input validation and output encoding. If no update is available, consider disabling the plugin until a fix is released, or implement web application firewall rules to block malicious parameter patterns.

Recommended fix High confidence

1.3.0

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find WP Directory Kit in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download version 1.3.0 from the WordPress plugin repository or your purchased source
  6. 6. If manually updating, deactivate the current plugin, delete the old version, then upload and activate version 1.3.0
  7. 7. After updating, clear any caching plugins or server-side caches
  8. 8. Test the plugin functionality to ensure the update did not break existing features

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29774 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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