dbcve.org
Advanced Woo SearchWordPress extension

CVE-2024-0251

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-13
Fix available
A fix is available. Upgrade to after 2.96 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The Advanced Woo Search plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the search parameter in all versions up to, and including, 2.96 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This only affects sites when the Dynamic Content for Elementor plugin is also installed.

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 confidence

The Advanced Woo Search WordPress plugin (versions up to 2.96) contains a reflected XSS vulnerability in its search parameter. The flaw stems from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript via malicious URLs. Successful exploitation requires the victim to click a crafted link. Notably, this vulnerability is only exploitable when the Dynamic Content for Elementor plugin is also installed on the same WordPress site.

MitigationUpdate Advanced Woo Search to the latest version beyond 2.96 to receive the patched code. If immediate patching is not possible, consider removing or deactivating the Dynamic Content for Elementor plugin until the update can be applied, and implement WAF rules to filter XSS payloads in search parameters.

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
Advanced Woo SearchWordPress extension
Affected:<= 2.96

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of Advanced Woo Search
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Advanced Woo Search' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin files in wp-content/plugins/advanced-woo-search/advanced-woo-search.php and look for the 'Version' header comment.
    Affected if The installed version is 2.96 or lower (any version up to and including 2.96).
  2. Check if Dynamic Content for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Dynamic Content for Elementor' or 'Dynamic.oto' in the list. If not visible in admin, check the plugin directory wp-content/plugins/ for a folder containing 'dynamic-content-for-elementor' or similar.
    Affected if The Dynamic Content for Elementor plugin is present on the same WordPress installation, regardless of its version.

You are affected if Advanced Woo Search version 2.96 or lower is installed AND Dynamic Content for Elementor plugin is also installed on the same WordPress site; both conditions must be true for the reflected XSS to be exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.96
Interim mitigation

Update Advanced Woo Search to the latest version beyond 2.96 to receive the patched code. If immediate patching is not possible, consider removing or deactivating the Dynamic Content for Elementor plugin until the update can be applied, and implement WAF rules to filter XSS payloads in search parameters.

Recommended fix High confidence

2.97 or later (latest stable release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Advanced Woo Search plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the updated plugin from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 2.97 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Advanced Woo Search Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0251 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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