dbcve.org
Woocommerce Products FilterWordPress extension · Woocommerce Filter

CVE-2018-8710

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-14
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A remote code execution issue was discovered in the WooCommerce Products Filter (aka WOOF) plugin before 2.2.0 for WordPress, as demonstrated by the shortcode parameter in a woof_redraw_woof action. The plugin implemented a page redraw AJAX function accessible to anyone without any authentication. WordPress shortcode markup in the "shortcode" parameters would be evaluated. Normally unauthenticated users can't evaluate shortcodes as they are often sensitive.

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 WooCommerce Products Filter plugin before 2.2.0 exposes an AJAX endpoint (woof_redraw_woof) accessible without authentication that processes a 'shortcode' parameter. Unauthenticated attackers can supply WordPress shortcode markup which gets evaluated server-side, bypassing the normal security restriction that prevents unauthenticated shortcode execution and potentially enabling remote code execution.

MitigationUpdate the WOOF plugin to version 2.2.0 or later which adds proper authentication to the AJAX endpoint. If immediate update is not possible, disable the plugin or implement firewall rules to block unauthenticated access to the vulnerable AJAX action.

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
Woocommerce Products FilterWordPress extension
Affected:< 2.2.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate the WOOF plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'woocommerce-filter-woof' or similar. Look for the main plugin file (usually index.php or the plugin's main PHP file) and open it to find the version header comment.
    Affected if The plugin folder exists and contains the WooCommerce Products Filter plugin files.
  2. Identify the installed plugin version
    Open the main plugin PHP file and locate the 'Version:' field in the plugin header comment at the top of the file. Alternatively, check the WordPress admin plugins list for the version number displayed for this plugin.
    Affected if The version number found is less than 2.2.0 (for example, 2.1.9, 2.1.8, etc.).
  3. Verify the vulnerable AJAX endpoint is exposed
    Make a POST request to your site's wp-admin/admin-ajax.php endpoint with the action parameter set to 'woof_redraw_woof'. You can use a tool like curl: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=woof_redraw_woof'. A response indicates the endpoint exists.
    Affected if The AJAX endpoint responds (returns any HTTP 200 response), meaning it is accessible without authentication.
  4. Confirm shortcode parameter processing is active
    Send a POST request to the same endpoint including a 'shortcode' parameter with test content, such as: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=woof_redraw_woof&shortcode=test'. Check if the server processes or echoes back the shortcode parameter value.
    Affected if The server accepts and processes the 'shortcode' parameter, confirming the vulnerable functionality is active.

You are affected if the WooCommerce Products Filter plugin is installed with a version lower than 2.2.0 AND the woof_redraw_woof AJAX endpoint is accessible without authentication and processes the shortcode parameter.

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 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Update the WOOF plugin to version 2.2.0 or later which adds proper authentication to the AJAX endpoint. If immediate update is not possible, disable the plugin or implement firewall rules to block unauthenticated access to the vulnerable AJAX action.

Recommended fix High confidence

WooCommerce Products Filter version 2.2.0 or later

  1. Backup your WordPress site and database before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'WooCommerce Products Filter' (WOOF) plugin
  4. Click 'Update now' if an update is available, or manually upload version 2.2.0 or later from wordpress.org
  5. After updating, verify the plugin version shows 2.2.0 or higher in the Plugins list
  6. Test that the frontend product filtering functionality works correctly

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

Fix this in Woocommerce Products Filter 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-2018-8710 — 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-2018-8710 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