Vulnerability in WP Directory Kit (WordPress plugin) (CVE-2025-13390)
Summary
Vulnerability in WP Directory Kit (WordPress plugin) (CVE-2025-13390). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-13390 has been found in WP Directory Kit (WordPress plugin).
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WP Directory Kit (WordPress plugin) CVE-2025-13390" on the vendor's site.
CVE-2025-13390 (WP Directory Kit (WordPress plugin)) — CWE-303 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-303) exists in WP Directory Kit (WordPress plugin).
Check the vendor advisory for the affected versions of WP Directory Kit (WordPress plugin).
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WP Directory Kit (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory security@wordfence.com
- exploit github.com
- exploit security@wordfence.com
- patch security@wordfence.com