DoofinderWordPress extension
CVE-2023-51678
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Doofinder Doofinder WP & WooCommerce Search.This issue affects Doofinder WP & WooCommerce Search: from n/a through 2.0.33.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Doofinder WP & WooCommerce Search plugin for WordPress allows attackers to induce authenticated users to perform unintended actions. The vulnerability affects all versions up to and including 2.0.33. Successful exploitation could allow attackers to modify search configuration or other plugin settings on the WooCommerce site.
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
<= 2.0.33CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 if Doofinder plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Doofinder WP & WooCommerce Search' or 'Doofinder' in the list. Note if it is installed and activated.Affected if The plugin is installed and activated on the WordPress site
-
Verify the installed plugin versionOn the Plugins page, click on the plugin name or view details to find the version number. Compare it to the affected range: any version <= 2.0.33 is vulnerable.Affected if The installed version is 2.0.33 or any earlier version
-
Confirm WooCommerce integration is activeCheck if WooCommerce is installed and activated, as this plugin extends WooCommerce search functionality. Go to Plugins and verify WooCommerce status.Affected if WooCommerce is active and the Doofinder plugin is managing search, providing a larger attack surface
-
Identify exposed admin endpointsCheck the plugin settings page at WooCommerce > Doofinder or under the Doofinder menu item in the admin dashboard. Look for any state-changing options like configuration save, index rebuild, or settings modification forms.Affected if The plugin exposes admin forms or AJAX endpoints that handle configuration changes without visible CSRF protection indicators
You are affected if the Doofinder WP & WooCommerce Search plugin is installed and running version 2.0.33 or any earlier version on your WordPress site.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing operations, validate the Referer header, and set SameSite attribute on session cookies. Ensure all form submissions and AJAX requests in the plugin include proper CSRF protection.
Fix this in Doofinder
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51678 — 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-51678 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