dbcve.org
Wp Directory KitWordPress extension · Wpdirectorykit

CVE-2025-13390

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to after 1.4.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Directory Kit WordPress plugin contains an authentication bypass vulnerability in the wdk_generate_auto_login_link function. The auto-login endpoint uses a cryptographically weak token generation mechanism that allows unauthenticated attackers to predict valid tokens and gain administrative access, enabling full site takeover.

MitigationUpdate the plugin to version 1.4.5 or later when available. If no update exists, disable the auto-login feature or add supplemental authentication controls. Review admin accounts for unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Directory KitWordPress extension
Affected:<= 1.4.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Directory Kit plugin installation and version
    Access WordPress admin dashboard under Plugins > Installed Plugins and locate 'WP Directory Kit', or inspect the plugin file /wp-content/plugins/wp-directory-kit/readme.txt for the 'Stable tag' version number
    Affected if The plugin is installed and the version number is 1.4.4 or lower
  2. Identify the auto-login endpoint exposure
    Check if the wdk_generate_auto_login_link function is accessible by testing access to the auto-login URL pattern (typically /?wdk_auto_login=1 or similar endpoint), or inspect the plugin source code for the auto-login handler
    Affected if The auto-login functionality exists and the endpoint is publicly accessible without authentication
  3. Inspect admin user accounts for unauthorized access
    Navigate to WordPress admin > Users > All Users and review all accounts with Administrator role, or query the wp_users and wp_usermeta database tables for unexpected admin-level accounts
    Affected if There are admin accounts that were not created by known, legitimate administrators
  4. Check for suspicious plugin modifications or backdoors
    Compare the plugin files in /wp-content/plugins/wp-directory-kit/ against a clean installation of the same version, or review recent file modifications using file integrity tools
    Affected if Plugin files have been modified unexpectedly or contain additional unauthorized files

A user is affected if WP Directory Kit version 1.4.4 or lower is installed and the auto-login feature is enabled, as this allows unauthenticated attackers to potentially predict valid tokens and gain administrative access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.4
Vendor patch plugins.trac.wordpress.org →
Interim mitigation

Update the plugin to version 1.4.5 or later when available. If no update exists, disable the auto-login feature or add supplemental authentication controls. Review admin accounts for unauthorized access.

Recommended fix High confidence

Version 1.4.5 or latest available release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP Directory Kit' in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/wp-directory-kit/ and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number is 1.4.5 or higher
  7. If the auto-login feature was in use, consider regenerating any existing auto-login tokens as a precautionary measure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Directory Kit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13390 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data