# CVE-2019-8404: File upload in n/a

> Attackers can upload malicious files via product images in Webiness Inventory, leading to code execution and content modification.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w48c-h4fc-5xvq

## What is CVE-2019-8404?

CVE-2019-8404 is a medium-severity vulnerability in n/a, published on 14 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Webiness Inventory 2.3. The ProductModel component allows Arbitrary File Upload via a crafted product image during the creation of a new product. Consequently, an attacker can steal information from the site with the help of an installed executable file, or change the contents of pages.

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

## Which versions are affected by CVE-2019-8404?

It affects 1 product.


Products: Webiness Inventory Project Webiness Inventory.

## How do I fix CVE-2019-8404?

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

## Is CVE-2019-8404 being exploited?

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

Public exploit code:

- Webiness Inventory 2.3 - 'ProductModel' Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8404 and fix it if it is affected.

What it is: CVE-2019-8404 is a medium-severity vulnerability in n/a, published on 14 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8404 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-2019-8404/ (Markdown: https://insights.sbomify.com/CVE-2019-8404/index.md)
```

## Sources

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

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