dbcve.org
Woocommerce Products FilterWordPress extension · Woocommerce Filter

CVE-2018-8711

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 local file inclusion 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 vulnerability is due to the lack of args/input validation on render_html before allowing it to be called by extract(), a PHP built-in function. Because of this, the supplied args/input can be used to overwrite the $pagepath variable, which then could lead to a local file inclusion attack.

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 version 2.2.0 contains a local file inclusion vulnerability caused by the lack of input validation on the render_html parameter before passing it to PHP's extract() function. This allows attackers to overwrite the $pagepath variable and include arbitrary local files from the server.

MitigationUpdate the WooCommerce Products Filter plugin to version 2.2.0 or later, which includes proper input validation to prevent variable overwriting via extract(). If immediate update is not possible, disable the woof_redraw_woof shortcode as a temporary measure.

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 WooCommerce Products Filter plugin installation
    Check your WordPress wp-content/plugins directory for a folder named 'woocommerce-filter' or similar. Common paths include /wp-content/plugins/woocommerce-filter/ or /wp-content/plugins/woof-woocommerce-products-filter/
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin file (usually index.php, woof.php, or similar in the plugin folder) and locate the version comment in the plugin header. Alternatively, check the readme.txt file for the 'Stable tag' entry
    Affected if The version number found is less than 2.2.0 (for example, 2.1.x, 2.0.x, or earlier)
  3. Verify the woof_redraw_woof shortcode is registered
    Search the plugin files for 'add_shortcode' and look for 'woof_redraw_woof' or similar shortcode registration. This shortcode handles the render_html parameter
    Affected if The shortcode is registered and accessible on the site
  4. Confirm the vulnerable extract() usage exists
    Search the plugin files for the string 'extract($_REQUEST' or 'extract($_POST' or 'extract($_GET' combined with references to 'render_html' or 'pagepath'. The vulnerability exists where extract() is called on user-controlled input without validation
    Affected if Code containing extract() being called on request parameters without sanitization is found in the plugin files

A user is affected if the WooCommerce Products Filter plugin version is below 2.2.0 AND the woof_redraw_woof shortcode is active, allowing the render_html parameter to be exploited for local file inclusion via the extract() function vulnerability.

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 WooCommerce Products Filter plugin to version 2.2.0 or later, which includes proper input validation to prevent variable overwriting via extract(). If immediate update is not possible, disable the woof_redraw_woof shortcode as a temporary measure.

Recommended fix High confidence

2.2.0

  1. Backup your WordPress site and database before updating any plugin
  2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. Locate WooCommerce Products Filter (WOOF) in the plugin list
  4. If automatic updates are enabled, the plugin should update to the latest version automatically. Otherwise, click 'Update Now' on the plugin
  5. Alternatively, download version 2.2.0 or later from the official WordPress plugin repository at wordpress.org/plugins/woocommerce-products-filter/ and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version by checking Plugins > Installed Plugins to confirm version 2.2.0 or newer is installed
  7. Test critical WooCommerce filter functionality to ensure the update did not break existing features

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

Fix this in Woocommerce Products Filter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8711 — 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-8711 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