DoofinderWordPress extension
CVE-2023-40602
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 Doofinder Doofinder WP & WooCommerce Search.This issue affects Doofinder WP & WooCommerce Search: from n/a through 1.5.49.
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 confidenceOpen redirect vulnerability in Doofinder WP & WooCommerce Search plugin allows attackers to craft malicious URLs that redirect users to untrusted external sites. This occurs due to insufficient validation of redirect parameters in the plugin.
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
DoofinderWordPress extension
<= 1.5.49CVSS 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.
-
Check installed plugin version in WordPress adminLog into WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Doofinder WP & WooCommerce Search' plugin, and note the version number displayed below the plugin nameAffected if The version shown is 1.5.49 or lower
-
Verify version via plugin filesAccess your site's files via FTP or file manager, navigate to /wp-content/plugins/doofinder-for-woocommerce/ or similar plugin directory, open the main PHP file (often doofinder.php or index.php) and locate the 'Version' header in the plugin comment blockAffected if The Version field reads 1.5.49 or lower
-
Confirm redirect feature exposureCheck if your site has any publicly accessible pages or URLs that include redirect parameters (such as 'redirect', 'url', or 'target' parameters) pointing to the Doofinder plugin endpointsAffected if The plugin's redirect functionality is exposed on your public site and accepts unvalidated URL parameters
You are affected if the Doofinder WP & WooCommerce Search plugin version installed on your WordPress site is 1.5.49 or lower and the redirect parameter feature is accessible.
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 · scopedUpdate Doofinder WP & WooCommerce Search plugin to the latest version (above 1.5.49) which contains proper URL validation to prevent untrusted redirects.
1.5.50 or later (contact vendor if unavailable)
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Doofinder WP & WooCommerce Search plugin
- 4. Check if an update is available. If an update to version 1.5.50 or later is available, click 'Update Now'
- 5. After updating, verify the plugin is running version 1.5.50 or higher
- 6. Test the search functionality to ensure the plugin continues to work correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Doofinder
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-40602 — 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-40602 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