Wp Directory KitWordPress extension · Wpdirectorykit
CVE-2023-41875
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 · uneditedMissing Authorization vulnerability in wpdirectorykit.com WP Directory Kit allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Directory Kit: from n/a through 1.2.6.
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 confidenceMissing authorization vulnerability in WP Directory Kit plugin allows attackers to exploit incorrectly configured access control security levels. The issue stems from missing or insufficient permission checks in certain functionality, likely enabling unauthenticated users to access privileged operations.
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
< 1.2.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if WP Directory Kit plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Directory Kit' by Wpdirectorykit, or check the file system at /wp-content/plugins/wp-directory-kit/ for the plugin directoryAffected if The plugin is installed and active
-
Determine installed plugin versionIn WordPress admin, find WP Directory Kit in the plugins list and view the version number displayed, or check the 'Version' field in the plugin's main PHP file headerAffected if Version is less than 1.2.7 (e.g., 1.2.6, 1.2.5, etc.)
-
Review access control security configurationsNavigate to plugin settings in WordPress admin panel and examine any access control, permission, or security level settings related to administrative or privileged functionsAffected if Access control settings are misconfigured or allow unauthorized access to privileged operations
-
Audit user role and capability settingsCheck WordPress user roles and capabilities configuration within the plugin to determine if proper authorization checks are enforced on sensitive operationsAffected if Plugin permits users without appropriate privileges to access administrative functions
User is affected if WP Directory Kit plugin version is below 1.2.7 AND access control configurations permit unauthorized access to privileged functions.
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.
dbcve · scoped1.2.7
Update WP Directory Kit to the latest version immediately. Additionally, conduct a code review to identify and enforce proper authorization checks on all sensitive functions and endpoints.
WP Directory Kit version 1.2.7
- Backup your WordPress site and database before making any changes
- Navigate to WordPress admin dashboard > Plugins
- Find WP Directory Kit in the installed plugins list
- Check if the current version is below 1.2.7
- If vulnerable, click 'Update now' to upgrade to version 1.2.7
- Alternatively, download version 1.2.7 from the official WordPress plugin repository and upload manually
- After updating, verify the plugin version shows 1.2.7 or higher
- Test that the access control functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Directory Kit
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41875 — 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-2023-41875 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