# CVE-2018-8711: Path traversal in n/a

> Attackers can exploit a local file inclusion vulnerability in the WooCommerce Products Filter plugin to read arbitrary files or execute code.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jp3g-72vx-f4gh

## What is CVE-2018-8711?

CVE-2018-8711 is a critical path traversal vulnerability in n/a, published on 14 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-8711?

It affects 1 product.


Products: Woocommerce-Filter Woocommerce Products Filter.

## How do I fix CVE-2018-8711?

No fix has been published for CVE-2018-8711 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-8711 being exploited?

There is no known exploitation of CVE-2018-8711 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-8710](https://insights.sbomify.com/CVE-2018-8710/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8711 and fix it if it is affected.

What it is: CVE-2018-8711 is a critical path traversal vulnerability in n/a, published on 14 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8711 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-8711/ (Markdown: https://insights.sbomify.com/CVE-2018-8711/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8711
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8711
- OSV: https://osv.dev/vulnerability/CVE-2018-8711

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-8711/
Summaries are generated and may contain mistakes; the official description above is the record.