CVE-2026-39534
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 · uneditedUnauthenticated Broken Access Control in WP Directory Kit <= 1.5.0 versions.
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 · moderate confidenceUnauthenticated broken access control vulnerability in WP Directory Kit WordPress plugin versions 1.5.0 and below. The plugin fails to properly enforce authorization checks, allowing unauthenticated attackers to access functionality or data they should not be able to reach.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check WP Directory Kit installed versionIn WordPress admin, navigate to Plugins > Installed Plugins. Locate WP Directory Kit and note the version number displayed. Alternatively, check the plugin's main PHP file header or version.php for the version constant.Affected if Version is 1.5.0 or lower.
-
Confirm plugin is activeVerify WP Directory Kit is currently enabled on the site. In Plugins > Installed Plugins, ensure the plugin does not have a deactivated or network-deactivated status.Affected if Plugin is active and version is 1.5.0 or below.
-
Identify accessible admin endpointsReview the plugin directory for PHP files in includes/ or controllers/ folders. Check for admin menu registrations (add_menu_page, add_submenu_page) and their associated page handlers. Note any endpoints under /wp-admin/admin.php?page=wdk or similar paths.Affected if Plugin exposes admin functionality without requiring WordPress login.
-
Audit REST API routesIf the plugin registers REST API routes, check the plugin code for rest_api_init hooks. Inspect route definitions for missing permission_callback functions or permission_callbacks that return true for unauthenticated users.Affected if REST routes exist and allow unauthenticated access to sensitive data or actions.
-
Check AJAX action handlersSearch plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ hooks. Identify any nopriv handlers that perform privileged operations without verifying user capabilities.Affected if AJAX actions registered with wp_ajax_noppriv_ perform access-controlled operations.
If WP Directory Kit is active at version 1.5.0 or below, the site is likely affected by this broken access control vulnerability that allows unauthenticated access to restricted functionality.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate WP Directory Kit to the latest available version. If no patch is available, consider disabling the plugin until a fix is released, or implement web application firewall rules to block suspicious unauthenticated requests.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39534 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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