Wp Directory KitWordPress extension · Wpdirectorykit
CVE-2023-31229
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in WP Directory Kit.This issue affects WP Directory Kit: from n/a through 1.1.9.
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 confidenceAn open redirect vulnerability in WP Directory Kit allows attackers to craft malicious URLs that redirect users to untrusted external sites. This occurs due to insufficient validation of redirect targets, enabling phishing attacks and unauthorized navigation.
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.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm WP Directory Kit plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP Directory Kit' in the list of active plugins.Affected if Plugin is present and active in the WordPress installation
-
Check installed plugin versionIn WordPress admin, click on the plugin name/link to view details, or inspect the main plugin file (typically wp-content/plugins/wp-directory-kit/wp-directory-kit.php) and look for the 'Version' header comment.Affected if Version number is lower than 1.2.0 (e.g., 1.1.x, 1.0.x)
-
Identify redirect functionality usageSearch plugin files for redirect-related functions (such as wp_redirect, wp_safe_redirect, or similar) and URL parameters that control redirect targets (common names include 'redirect', 'url', 'target', 'goto').Affected if Plugin contains redirect logic that accepts user-controlled URLs without strict validation
User is affected if WP Directory Kit is installed with version lower than 1.2.0 and the plugin's redirect feature is in use.
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.0
Update WP Directory Kit to the latest version which contains proper redirect URL validation. If no patch is available, implement server-side validation to ensure redirect targets are relative paths or trusted domains.
WP Directory Kit 1.2.0 or later
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins
- Find WP Directory Kit in the plugins list
- Click 'Update now' if an update is available, or manually upload version 1.2.0 or later
- Verify the plugin version is 1.2.0 or higher after updating
- Test that the open redirect vulnerability is no longer exploitable
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
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31229 — 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-31229 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