# CVE-2021-46113: File upload in n/a

> Attackers can achieve remote code execution by uploading malicious PHP files to the KEA-Hotel-ERP web application.

- **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:** 25 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x44j-rvwf-fj2w

## What is CVE-2021-46113?

CVE-2021-46113 is a high-severity vulnerability in n/a, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In MartDevelopers KEA-Hotel-ERP open source as of 12-31-2021, a remote code execution vulnerability can be exploited by uploading PHP files using the file upload vulnerability in this service.

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

## Which versions are affected by CVE-2021-46113?

It affects 1 product.


Products: Kea-Hotel-Erp Project Kea-Hotel-Erp.

## How do I fix CVE-2021-46113?

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

## Is CVE-2021-46113 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46113 and fix it if it is affected.

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

## Sources

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

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