Security readout for executives and security teams
Plain-English summary
CVE-2018-8711 affects older WooCommerce Products Filter (WOOF) plugin versions before 2.2.0 for WordPress. A validation flaw could allow local file inclusion through plugin input handling. For executives, the business risk is to WordPress stores still running outdated plugin code, not all WooCommerce sites.
Executive priority
Address during routine vulnerability remediation, with faster handling for internet-facing ecommerce sites. The issue is old and has a named fixed version, but severity data and exploitation evidence are incomplete in the supplied sources.
Technical view
The CVE describes local file inclusion in WOOF before 2.2.0. Insufficient args/input validation in render_html before extract() could let supplied input overwrite $pagepath, enabling local file inclusion. The bundle does not provide CVSS, authentication requirements, or confirmed exploitation details.
Likely exposure
Exposure is likely limited to WordPress sites with WooCommerce Products Filter/WOOF installed below version 2.2.0. The source bundle does not establish default exploitability, authentication requirements, or affected hosting configurations.
Exploitation context
The CVE is not listed as CISA KEV in the supplied data. A public advisory exists, but the bundle does not cite active exploitation. Treat public-facing stores with outdated WOOF versions as higher priority for inventory and upgrade validation.
Researcher notes
Key validation point is version exposure: WOOF before 2.2.0. The described root cause is unsafe input handling before extract(), allowing $pagepath overwrite and possible local file inclusion. Do not assume unauthenticated exploitation without additional source evidence.
Mitigation direction
- Upgrade WooCommerce Products Filter/WOOF to version 2.2.0 or later.
- Check current vendor guidance before applying operational compensating controls.
- Disable or remove the plugin if it cannot be safely updated.
- Review WordPress and web server logs for suspicious plugin requests.
- Prioritize externally reachable ecommerce sites first.
Validation and detection
- Inventory WordPress sites for the WOOF plugin.
- Confirm the installed plugin version is 2.2.0 or later.
- Check whether the plugin is active on public-facing stores.
- Review change records for the March 2018 update window.
- Verify no unsupported fork or pinned vulnerable copy remains.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-8711 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/woocommerce-products-filter/#developersCVE reference · x_refsource_MISC
- https://sec-consult.com/en/blog/advisories/arbitrary-shortcode-execution-local-file-inclusion-in-woof-pluginus-net/index.htmlCVE reference · x_refsource_MISC
- https://www.woocommerce-filter.com/update-woocommerce-products-filter-v-2-2-0/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
