# CVE-2026-94104: NivoCart through 2.4.0 Arbitrary File Upload RCE via filemanager

> Attackers with back-office view access can upload PHP files to execute remote code due to missing extension validation in the file manager.

- **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:** 20 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-m76p-p4wh-76x9

## What is CVE-2026-94104?

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

### Official description

NivoCart through 2.4.0 contains an arbitrary file upload vulnerability in the File Manager multi() endpoint that fails to validate file extensions for new filenames or when chunks parameter is 2 or higher. Attackers with view-only back-office access can upload PHP files to the web-accessible image/data/ directory and execute them for remote code execution.

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

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


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

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

## Is CVE-2026-94104 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94104 is a high-severity vulnerability in nivocart, published on 20 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94104 in the wild and no public exploit code.

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

## Sources

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

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