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

> Logged-in admins can upload PHP files to achieve remote code execution due to missing file extension validation in the upload endpoint.

- **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:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-6jhf-4357-9q99

## What is CVE-2026-88396?

CVE-2026-88396 is a high-severity vulnerability in n/a, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ApiAdmin v5.0 and before is vulnerable to Directory Traversal. The admin file-upload endpoint POST /admin/Index/upload in ApiAdmin takes the uploaded file's extension verbatim there is no whitelist, blacklist or content check and move_uploaded_file() drops the file into the web-accessible directory public/upload/Ymd/. Any logged-in admin user can upload a .php file and reach it directly over HTTP, achieving remote code execution on the server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-88396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88396 is a high-severity vulnerability in n/a, published on 5 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-88396 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-2026-88396/ (Markdown: https://insights.sbomify.com/CVE-2026-88396/index.md)
```

## Sources

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

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