# CVE-2026-67206: Wolf CMS 0.8.3.1 Authenticated RCE via FileManagerController File Upload

> Authenticated attackers can upload malicious PHP files to execute arbitrary code on Wolf CMS installations.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-3pqf-wrr6-rf9m

## What is CVE-2026-67206?

CVE-2026-67206 is a high-severity vulnerability in wolfcms, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wolf CMS through 0.8.3.1 contains a remote code execution vulnerability in FileManagerController that allows authenticated attackers to create arbitrary PHP files by exploiting missing file extension validation in the create_file() and save() functions. Attackers with the file_manager_mkfile capability can write malicious PHP content into the web-accessible FILES_DIR directory and trigger execution by requesting the file over HTTP.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-67206 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67206 exists.

Public exploit code:

- Wolf CMS <= 0.8.3.1 - RCE via Arbitrary File Write (github_poc): https://github.com/anirbala98/CVE-2026-67206
- Wolf CMS 0.8.3.1 - RCE v (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67206 is a high-severity vulnerability in wolfcms, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67206 exists.

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

## Sources

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

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