# CVE-2025-13390: WP Directory Kit <= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover

> Unauthenticated attackers can gain administrative access and take over the site via a predictable auto-login token in WP Directory Kit.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-cmp6-j4f4-vm9f

## What is CVE-2025-13390?

CVE-2025-13390 is a critical authentication bypass vulnerability in listingthemes WP Directory Kit, published on 3 Dec 2025. 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 authentication bypass in all versions up to, and including, 1.4.4 due to incorrect implementation of the authentication algorithm in the "wdk_generate_auto_login_link" function. This is due to the feature using a cryptographically weak token generation mechanism. This makes it possible for unauthenticated attackers to gain administrative access and achieve full site takeover via the auto-login endpoint with a predictable token.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

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

It affects 1 product.


Products: Wpdirectorykit Wp Directory Kit.

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

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

## Is CVE-2025-13390 being exploited?

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

Public exploit code:

- WP Directory Kit <= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover (github_poc): https://github.com/Nxploited/CVE-2025-13390
- WP Directory Kit <= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover (github_poc): https://github.com/d0n601/CVE-2025-13390
- WP Directory Kit <= 1.4.4 - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-13390.yaml

## Other vulnerabilities in listingthemes WP Directory Kit

- [CVE-2023-2278](https://insights.sbomify.com/CVE-2023-2278/): WP Directory Kit <= 1.1.9 - Unauthenticated Local File Inclusion via wdk_public_action (critical 9.8)
- [CVE-2024-3217](https://insights.sbomify.com/CVE-2024-3217/): WP Directory Kit <= 1.3.0 - Authenticated (Subscriber+) SQL Injection (high 8.8)
- [CVE-2024-37487](https://insights.sbomify.com/CVE-2024-37487/): WordPress WP Directory Kit plugin <= 1.3.5 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-29774](https://insights.sbomify.com/CVE-2024-29774/): WordPress WP Directory Kit plugin <= 1.2.9 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2023-2351](https://insights.sbomify.com/CVE-2023-2351/): Missing authorization in WP Directory Kit (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13390 is a critical authentication bypass vulnerability in listingthemes WP Directory Kit, published on 3 Dec 2025. 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-13390 exists.

Affected product: listingthemes 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-13390/ (Markdown: https://insights.sbomify.com/CVE-2025-13390/index.md)
```

## Sources

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

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