# CVE-2025-13920: WP Directory Kit <= 1.4.9 - Unauthenticated Email Exposure via wdk_public_action

> Unauthenticated attackers can extract email addresses of users with specific roles via the AJAX handler in WP Directory Kit.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7wpw-5pc9-jh59

## What is CVE-2025-13920?

CVE-2025-13920 is a medium-severity vulnerability in wpdirectorykit WP Directory Kit, published on 24 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-13920?


## How do I fix CVE-2025-13920?

No fix has been published for CVE-2025-13920 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13920 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13920 exists.

Public exploit code:

- WP Directory Kit < 1.5.0 - Unauthenticated Email Exposure (nuclei): http/cves/2025/CVE-2025-13920.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13920 and fix it if it is affected.

What it is: CVE-2025-13920 is a medium-severity vulnerability in wpdirectorykit WP Directory Kit, published on 24 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13920 exists.

Affected product: wpdirectorykit WP Directory Kit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13920/ (Markdown: https://insights.sbomify.com/CVE-2025-13920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13920
- OSV: https://osv.dev/vulnerability/CVE-2025-13920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13920/
Summaries are generated and may contain mistakes; the official description above is the record.