Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running WP Directory Kit ≤1.4.4
-
DeliveryPredict weak auto-login token
-
ExploitSubmit token to auto-login endpoint
-
ExecutionObtain administrator session
-
PersistUpload malicious plugin/PHP for code execution
-
ImpactFull site takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication algorithm review
|
| Exploitation Conditions | The target site must have the WP Directory Kit plugin installed and active at version ≤1.4.4 (EUVD: 1.4.0 through 1.4.4), and the auto-login link feature backed by the vulnerable wdk_generate_auto_login_link function must be reachable at its auto-login endpoint. Exploitation requires no authentication, no user interaction, and works against default deployments because the token-generation mechanism itself is cryptographically weak and predictable - there is no configuration hardening that the description identifies as mitigating short of patching. The practical limiting factor is purely footprint: only sites running this specific plugin and version range are affected, not WordPress generally. |
| Impact | Signals converge on genuine high priority. The CVSS 9.8 vector (AV:N/AC:L/PR:N/UI:N) describes remote, unauthenticated, low-complexity exploitation with full C/I/A impact, and this is corroborated by the description: a cryptographically weak, predictable token in the auto-login endpoint yields direct administrative access and full site takeover - a CWE-303 authentication-bypass that matches the vector cleanly with no contradiction between vector and prose. Publicly available exploit code (two independent write-ups plus a GitHub PoC) lowers the skill barrier, and a vendor patch exists, which typically accelerates reverse-engineering and opportunistic mass scanning of WordPress plugins. The one tempering signal is EPSS: 0.66% (71st percentile) is modest and not yet in KEV, indicating that observed/predicted real-world exploitation volume is still limited rather than widespread - likely because the affected product is a single plugin with a bounded install base rather than because exploitation is hard. No SSVC decision data was provided in the input, so the SSVC exploitation/automatable/technical-impact framing cannot be independently stated. Net: treat as an urgent patch item for any site running this plugin (trivial full compromise, public PoC), while recognizing EPSS suggests the absolute number of targets is limited rather than internet-wide. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a WordPress site running WP Directory Kit ≤1.4.4, computes or guesses the predictable auto-login token because of the weak token-generation algorithm, and submits it to the auto-login endpoint. The server grants an authenticated administrator session, giving the attacker full site takeover (plugin/theme upload, PHP code execution, user manipulation). Public exploit code (GitHub d0n601 PoC and two technical write-ups) makes this reproducible with minimal effort given AV:N/AC:L. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 18, 2026
An authentication bypass in the WP Directory Kit WordPress plugin through version 1.4.4 lets unauthenticated remote attackers log in as an administrator by predicting the token produced by the wdk_generate_auto_login_link function, resulting in full site takeover. The root cause is a cryptographically weak token generation scheme used by the plugin's auto-login link feature, which makes the resulting credentials guessable rather than secret. Publicly available exploit code exists (including a dedicated GitHub repository and a technical write-up), and the vendor has released a patched build, though EPSS currently estimates roughly a 0.66% chance of exploitation in the next 30 days (71st percentile).
Earlier versions of this analysis (1)
RemediationAI
Upgrade WP Directory Kit to a release newer than 1.4.4 - the vendor fix is published in the plugin Trac changeset 3400599 (https://plugins.trac.wordpress.org/changeset/3400599/wpdirectorykit/), so install the first tagged version that includes it and verify the deployed plugin file no longer contains the weak wdk_generate_auto_login_link token logic. Until the update is applied, the most effective compensating control is to deactivate the plugin outright (side effect: directory/listing functionality goes offline); if that is not feasible, disable or block access to the plugin's auto-login endpoint at the reverse proxy or WAF and rotate all administrator credentials and session tokens, since a predictable token may already have been used. Restricting /wp-admin and the plugin endpoint by IP allow-listing reduces exposure but breaks legitimate remote administration and does not remove the underlying weak token generation, so it should be treated as temporary only. Monitor administrator accounts and new user creation for signs of unauthorized access while unpatched.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-303 (Incorrect Implementation of Authentication Algorithm) inside the WordPress plugin ecosystem. Rather than a memory-safety bug, the defect is architectural: WP Directory Kit's auto-login convenience feature mints authentication links inside wdk_generate_auto_login_link, but the token it derives is generated with a cryptographically weak mechanism, so its value can be predicted or reconstructed by an attacker without any secret material. Because the token is the sole credential gating the auto-login endpoint, a predictable token collapses the entire authentication decision - the plugin effectively authenticates the attacker as whichever user (notably an administrator) the link is bound to. The CPE cpe:2.3:a:wpdirectorykit:wp_directory_kit:*:*:*:*:*:wordpress:*:* confirms the affected surface is the WordPress plugin distribution, and EUVD scopes affected releases to 1.4.0 through 1.4.4. Any code path reusing this generator inherits the same weakness.
Know when Wp Directory Kit gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Predictable token is computed and submitted remotely with no auth or interaction (AV:N/AC:L/PR:N/UI:N), yielding administrative takeover with full C/I/A; scope unchanged as impact stays within the WordPress instance.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionNVD
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.
Executive ViewAI
The WP Directory Kit plugin contains a critical authentication bypass vulnerability (CVSS 10.0) that allows unauthenticated attackers to gain administrative access to WordPress sites, resulting in complete site compromise. Any organization using this plugin is at immediate risk of data breach, malware injection, and operational disruption. This vulnerability has a public exploit available and affects all versions through 1.4.4.
Apply vendor patch. If patching is delayed: (1) Disable WP Directory Kit plugin entirely until patched; (2) Implement WAF rules to block requests to the auto-login endpoint (/wdk-auto-login or similar); (3) Restrict WordPress admin dashboard access by IP whitelist; (4) Enable comprehensive logging and alerting on administrative account activities and plugin authentication functions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Wp Directory Kit
View allThe WP Directory Kit plugin for WordPress is vulnerable to SQL Injection via the 'attribute_value' and 'attribute_id' pa
Unauthenticated SQL injection in WP Directory Kit WordPress plugin (all versions before 1.5.6) allows remote attackers t
SQL injection in WP Directory Kit WordPress plugin (all versions before 1.5.6) allows any authenticated user - including
The WP Directory Kit plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 1.1.9
SQL injection via an unsecured AJAX endpoint in WP Directory Kit (WordPress plugin) before 1.5.5 allows any authenticate
WP Directory Kit versions before 1.5.5 expose the plugin's full settings - including sensitive API keys and third-party
SQL injection in WP Directory Kit WordPress plugin before 1.5.7 is exploitable by authenticated administrators, with mat
Stored cross-site scripting in the WP Directory Kit WordPress plugin before version 1.5.8 lets an authenticated user who
SQL injection in the WP Directory Kit WordPress plugin (versions through 1.5.7) lets authenticated users with page-build
Unauthorized data exposure in the WP Directory Kit WordPress plugin (all versions before 1.5.5) allows any authenticated
WP Directory Kit WordPress plugin before version 1.5.5 exposes sensitive site data to any authenticated user due to miss
The WP Directory Kit plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a m
EUVD-2025-200972
NVD
CVE.org
EPSS
GitHub
Exploit-DB