# CVE-2026-88419: File upload in n/a

> Authenticated low-privileged users can upload malicious PHP files to execute arbitrary code on the server due to missing extension validation in WuzhiCMS.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-r6cc-qh78-7796

## What is CVE-2026-88419?

CVE-2026-88419 is a high-severity vulnerability in n/a, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An unrestricted upload of files with a dangerous type in the thumbnail-upload endpoint (/index.php?m=member&f=article&v=thumbUpload) of WuzhiCMS 5.0.0 allows an authenticated low-privileged member to upload a crafted .php file and execute arbitrary PHP code on the server, because the stored file extension is taken verbatim from the client-supplied filename with no extension allowlist or content validation and the file is written to the web-accessible uploadfile/ directory, from which the web server executes PHP.

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

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


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

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

## Is CVE-2026-88419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88419 is a high-severity vulnerability in n/a, published on 22 Sep 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-88419 exists.

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

## Sources

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

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