# CVE-2017-18048: File upload in n/a

> Attackers can upload malicious files with uppercase extensions to execute arbitrary code on Monstra CMS servers.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 23 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9gjw-qvrh-6f5r

## What is CVE-2017-18048?

CVE-2017-18048 is a high-severity vulnerability in n/a, published on 23 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Monstra CMS 3.0.4 allows users to upload arbitrary files, which leads to remote command execution on the server, for example because .php (lowercase) is blocked but .PHP (uppercase) is not.

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

## Which versions are affected by CVE-2017-18048?

It affects 1 product.


Products: Monstra Monstra.

## How do I fix CVE-2017-18048?

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

## Is CVE-2017-18048 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-18048 exists.

Public exploit code:

- Monstra CMS Authenticated Arbitrary File Upload (metasploit)

## Other vulnerabilities in n/a

- [CVE-2021-40940](https://insights.sbomify.com/CVE-2021-40940/): File upload in n/a (critical 9.8)
- [CVE-2021-36548](https://insights.sbomify.com/CVE-2021-36548/): File upload in n/a (critical 9.8)
- [CVE-2020-25414](https://insights.sbomify.com/CVE-2020-25414/): Code injection in n/a (critical 9.8)
- [CVE-2020-13384](https://insights.sbomify.com/CVE-2020-13384/): File upload in n/a (high 8.8)
- [CVE-2018-16608](https://insights.sbomify.com/CVE-2018-16608/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18048 and fix it if it is affected.

What it is: CVE-2017-18048 is a high-severity vulnerability in n/a, published on 23 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-18048 exists.

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-2017-18048/ (Markdown: https://insights.sbomify.com/CVE-2017-18048/index.md)
```

## Sources

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

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