Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-13390 is a critical-severity Incorrect Implementation of Authentication Algorithm (CWE-303) vulnerability in Wpdirectorykit Wp Directory Kit. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique External Remote Services (T1133); ranked in the top 9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-13390 is an authentication bypass vulnerability affecting the WP Directory Kit plugin for WordPress in all versions up to and including 1.4.4. The issue stems from an incorrect implementation of the authentication algorithm in the "wdk_generate_auto_login_link" function, which relies on a cryptographically weak token generation mechanism. This flaw results in predictable tokens that can be leveraged via the auto-login endpoint, earning a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) and mapping to CWE-303 (Incorrect Implementation of Authentication Algorithm).
Unauthenticated attackers can exploit this vulnerability remotely over the network with low complexity and no user interaction required. By predicting the weak token, they can access the auto-login endpoint to bypass authentication entirely, gaining administrative privileges and achieving full site takeover, including arbitrary code execution, data exfiltration, or site defacement.
Advisories from sources like Wordfence and the WordPress plugin trac recommend updating the WP Directory Kit plugin beyond version 1.4.4, with a specific patch referenced in trac changeset 3400599. Additional details on the vulnerability and proof-of-concept are available in researcher repositories such as GitHub/d0n601/CVE-2025-13390 and ryankozak.com/posts/cve-2025-13390.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-200972
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages directly uncovers incorrect implementations of required authentication algorithms.
Requiring documented development processes, standards, and tools reduces the chance that an established authentication algorithm is coded incorrectly.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct implementation of authentication algorithms.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure authentication control directly requires correct implementation of authentication algorithms.
Security testing can detect flawed authentication implementations but does not prevent them by itself.
Cryptography control addresses proper use of authentication algorithms but is broader than authentication alone.
Secure development lifecycle includes verification steps that can catch incorrect authentication implementations.
Application security requirements can specify correct authentication algorithm use but do not guarantee correct implementation.
Secure coding practices reduce the likelihood of incorrect authentication algorithm implementation.