WP Directory Kit <= 1.2.2 - Missing Authorization to Plugin Installation, Settings Change/Delete, Demo Import, Directory Kit Deletion via wdk_public_action
Strategic Overview
- Status
- Patched in 1.2.3
- Affected Plugin
- WP Directory Kit
- Affected Version
<= 1.2.2- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-2280
At a glance
CVE-2023-2280 is a medium-severity Missing Authorization vulnerability in the WP Directory Kit WordPress plugin, affecting versions <= 1.2.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.3; sites on affected versions should update now. Disclosed May 2023, reported by Ram.
Vulnerability Overview
The WP Directory Kit plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'ajax_public' function in versions up to, and including, 1.2.2. This makes it possible for unauthenticated attackers to delete or change plugin settings, import demo data, delete Directory Kit related posts and terms, and install arbitrary plugins. A partial patch was introduced in version 1.2.0 and an additional partial patch was introduced in version 1.2.2, but the issue was not fully patched until 1.2.3.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Directory Kit <= 1.2.2 carries this weakness at ajax_public, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Directory Kit the fix is 1.2.3: builds <= 1.2.2 are affected, anything from 1.2.3 onward is not.
Remediation
Update to version 1.2.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Directory Kit 1.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.5CVE-2023-2351: WP Directory Kit Plugin Settings Change/Delete, Demo
CVE-2023-2351 - 5.3CVE-2026-39534: WP Directory Kit <= 1.5.0 Missing Authorization
CVE-2026-39534 - 5.3CVE-2025-60120: WP Directory Kit <= 1.4.0 Missing Authorization
CVE-2025-60120 - 5.3CVE-2023-41875: WP Directory Kit <= 1.2.6 Missing Authorization
CVE-2023-41875
Other vulnerabilities in WP Directory Kit
- 10.0CVE-2025-13390: WP Directory Kit Authentication Bypass
CVE-2025-13390 - 9.8CVE-2023-2278: WP Directory Kit <= 1.1.9 Local File Inclusion
CVE-2023-2278 - 8.8CVE-2024-3217: WP Directory Kit <= 1.3.0 SQL Injection
CVE-2024-3217 - 7.5CVE-2026-28001: Directory Kit <= 1.5.4 SQL Injection
CVE-2026-28001 - 7.5CVE-2026-18474: Directory Kit <= 1.5.5 SQL Injection
CVE-2026-18474 - 7.5CVE-2026-18473: Directory Kit <= 1.5.4 SQL Injection
CVE-2026-18473 - 7.5CVE-2026-42672: WP Directory Kit <= 1.5.1 SQL Injection
CVE-2026-42672 - 7.5CVE-2026-39531: WP Directory Kit <= 1.5.0 SQL Injection
CVE-2026-39531
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C