CVE-2025-13920
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 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.9 via the wdk_public_action AJAX handler. This makes it possible for unauthenticated attackers to extract email addresses for users with Directory Kit-specific user roles.
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 · high confidenceThe WP Directory Kit WordPress plugin has an unauthenticated sensitive information exposure vulnerability in the wdk_public_action AJAX handler. Attackers can exploit this to extract email addresses of users with Directory Kit-specific roles. The flaw affects all versions up to and including 1.4.9.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Verify WP Directory Kit plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP Directory Kit' in the list of active plugins.Affected if The plugin is installed and active in WordPress.
-
Check installed plugin versionIn the Plugins list, click on WP Directory Kit to view the plugin details. Note the version number displayed, or check the plugin header in /wp-content/plugins/wp-directory-kit/ directory via file manager or FTP.Affected if The installed version is 1.4.9 or any earlier version (1.0.x through 1.4.9).
-
Confirm AJAX endpoint is publicly accessibleSend a GET or POST request to /wp-admin/admin-ajax.php?action=wdk_public_action without providing authentication credentials. Use a tool like curl: curl -s 'https://yourdomain.com/wp-admin/admin-ajax.php?action=wdk_public_action'.Affected if The endpoint responds without requiring login (HTTP 200 OK), indicating the vulnerable handler is exposed to unauthenticated users.
-
Check for Directory Kit user rolesNavigate to Users > Users in WordPress admin. Review the user roles column for any custom Directory Kit roles such as 'WDK Agent', 'WDK Listing Owner', or similar custom roles added by the plugin.Affected if Users exist with Directory Kit-specific custom roles, as these are the targets for email extraction.
Your environment is affected if WP Directory Kit version 1.4.9 or earlier is installed, the wdk_public_action AJAX endpoint is accessible without authentication, and users with Directory Kit-specific roles exist in the system.
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.
From vendor dataUpdate WP Directory Kit to a version beyond 1.4.9 to patch the vulnerability. If an update is unavailable, implement custom authorization checks on the wdk_public_action AJAX handler to restrict unauthenticated access to user data.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13920 — 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-2025-13920 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