DoofinderWordPress extension
CVE-2023-49185
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Doofinder Doofinder WP & WooCommerce Search allows Reflected XSS.This issue affects Doofinder WP & WooCommerce Search: from n/a through 2.1.7.
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 · high confidenceA reflected cross-site scripting (XSS) vulnerability in the Doofinder WP & WooCommerce Search plugin allows attackers to inject malicious scripts through unsanitized user input that gets reflected in web pages generated by the plugin. The CVSS 6.1 score indicates the vulnerability is exploitable via user interaction (e.g., tricking a user into clicking a crafted link).
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.1.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
- 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.
-
Verify Doofinder plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Doofinder WP & WooCommerce Search' or 'Doofinder' in the plugin list.Affected if The plugin appears in the installed plugins list.
-
Check installed plugin versionIn the Plugins page, click on the plugin name or view details to find the version number. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/doofinder-for-woocommerce/ or similar path) for the 'Version' header in the plugin comment block.Affected if The version number is 2.1.7 or lower.
-
Confirm plugin is activeOn the Plugins > Installed Plugins page, verify that the Doofinder plugin shows as 'Active' (not just installed but deactivated).Affected if The plugin is active and serving search functionality on the site.
-
Identify reflected input vectorsReview plugin settings for any search parameters or user-customizable text that gets displayed back in search results pages. Common XSS vectors in search plugins include query parameters like 's', 'search', or 'dfParam' that might be reflected in the page HTML.Affected if The plugin reflects any user-supplied input (such as search terms) back into the rendered HTML without sanitization.
You are affected if the Doofinder plugin version is 2.1.7 or lower AND the plugin is active, allowing unsanitized user input to be reflected in search result pages.
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 dataUpdate the Doofinder plugin to version 2.1.8 or later, which should include proper input sanitization and output encoding. If no update is available, manually review and sanitize all user-supplied input in the plugin's frontend rendering code.
Fix this in Doofinder
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49185 — 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-49185 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