# CVE-2026-86787: Affiliate Toolkit 3.8.7 - 3.9.0 - Contributor+ RCE via BladeOne @php Directive

> Low-privileged users can execute arbitrary PHP code via the templating engine, requiring an upgrade to the latest plugin version.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-rwr2-57r9-hfq7

## What is CVE-2026-86787?

CVE-2026-86787 is a high-severity code injection vulnerability in Unknown affiliate-toolkit, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The affiliate-toolkit  WordPress plugin before 3.9.1 does not prevent a low-privileged user from supplying a template body that its bundled templating engine compiles and executes as PHP, allowing users with the Contributor role or above to run arbitrary PHP code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-86787?


## How do I fix CVE-2026-86787?

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

## Is CVE-2026-86787 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86787 and fix it if it is affected.

What it is: CVE-2026-86787 is a high-severity code injection vulnerability in Unknown affiliate-toolkit, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86787 in the wild and no public exploit code.

Affected product: Unknown affiliate-toolkit. 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-2026-86787/ (Markdown: https://insights.sbomify.com/CVE-2026-86787/index.md)
```

## Sources

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

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