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

> Unauthenticated attackers can upload executable files to the server via the recruitment module, leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v9q3-wwmw-45rq

## What is CVE-2019-15130?

CVE-2019-15130 is a critical vulnerability in n/a, published on 18 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Recruitment module in Humanica Humatrix 7 1.0.0.203 and 1.0.0.681 allows an unauthenticated attacker to upload any file type to a candidate's profile picture folder via a crafted recruitment_online/personalData/act_personaltab.cfm multiple-part POST request with a predictable WRC01_USERID parameter. Moreover, the attacker can upload executable content (e.g., asp or aspx) for executing OS commands on the server.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Humanica Humatrix 7.

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

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

## Is CVE-2019-15130 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14932](https://insights.sbomify.com/CVE-2019-14932/): Auth bypass in n/a (high 7.5)
- [CVE-2019-15129](https://insights.sbomify.com/CVE-2019-15129/): Missing authorization in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15130 is a critical vulnerability in n/a, published on 18 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15130 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-15130/ (Markdown: https://insights.sbomify.com/CVE-2019-15130/index.md)
```

## Sources

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

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