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

> Authenticated attackers can bypass file upload restrictions to upload webshells and execute arbitrary code on Sentrifugo HRMS.

- **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:** 4 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pqx5-mp9c-hm3r

## What is CVE-2019-15813?

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

### Official description

Multiple file upload restriction bypass vulnerabilities in Sentrifugo 3.2 could allow authenticated users to execute arbitrary code via a webshell.

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

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

It affects 1 product.


Products: Sentrifugo Sentrifugo.

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

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

## Is CVE-2019-15813 being exploited?

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

Public exploit code:

- This container was made to explain and demonstrate how CVE-2019-15813 (Sentrifugo works) (github_poc): https://github.com/wolf1892/CVE-2019-15813
- Sentrifugo 3.2 - File Upload Restriction Bypass (exploitdb)
- Sentrifugo 3.2 - File Upload Restriction Bypass (Authenticated) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-15814](https://insights.sbomify.com/CVE-2019-15814/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15813 is a high-severity vulnerability in n/a, published on 4 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15813 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-15813/ (Markdown: https://insights.sbomify.com/CVE-2019-15813/index.md)
```

## Sources

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

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