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

> Authenticated attackers can execute arbitrary code by uploading a PHP shell via the admin commandr interface in Composr CMS.

- **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:** 9 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-45x9-545x-8mc3

## What is CVE-2021-46360?

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

### Official description

Authenticated remote code execution (RCE) in Composr-CMS 10.0.39 and earlier allows remote attackers to execute arbitrary code via uploading a PHP shell through /adminzone/index.php?page=admin-commandr.

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

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

It affects 1 product.


Products: Ocproducts Composr.

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

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

## Is CVE-2021-46360 being exploited?

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

Public exploit code:

- Composr-CMS Version <=10.0.39 - Authenticated Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-30149](https://insights.sbomify.com/CVE-2021-30149/): File upload in n/a (critical 9.8)
- [CVE-2021-30150](https://insights.sbomify.com/CVE-2021-30150/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46360 is a high-severity vulnerability in n/a, published on 9 Feb 2022. 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-2021-46360 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-2021-46360/ (Markdown: https://insights.sbomify.com/CVE-2021-46360/index.md)
```

## Sources

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

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