# CVE-2018-8710: Code injection in n/a

> Unauthenticated attackers can execute arbitrary code via shortcode injection in the WooCommerce Products Filter plugin's AJAX redraw function.

- **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:** 16 Sep 2024
- **Also known as:** GHSA-mvhg-g9jx-74w2

## What is CVE-2018-8710?

CVE-2018-8710 is a critical code injection 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 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.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Woocommerce-Filter Woocommerce Products Filter.

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

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

## Is CVE-2018-8710 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-8711](https://insights.sbomify.com/CVE-2018-8711/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8710 is a critical code injection 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-8710 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-8710/ (Markdown: https://insights.sbomify.com/CVE-2018-8710/index.md)
```

## Sources

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

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