# CVE-2021-46062: MCMS Arbitrary File Deletion vulnerability

> An attacker can delete arbitrary files in MCMS via the oldFileName component, potentially compromising data integrity.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rpvr-mw7r-25xx

## What is CVE-2021-46062?

CVE-2021-46062 is a high-severity path traversal vulnerability in n/a, published on 18 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

MCMS v5.2.5 was discovered to contain an arbitrary file deletion vulnerability via the component oldFileName.

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

4 open source packages ship an affected version, including net.mingsoft:ms-basic and net.mingsoft:ms-mcms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net.mingsoft:ms-basic` | Maven | All versions | 2.1.16 |
| `net.mingsoft:ms-basic` | Maven | All versions | 2.1.16 |
| `net.mingsoft:ms-mcms` | Maven | All versions | 5.2.11 |
| `net.mingsoft:ms-mcms` | Maven | All versions | 5.2.11 |

Products: Mingsoft Mcms.

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

Upgrade net.mingsoft:ms-basic to 2.1.16 or later.

## Is CVE-2021-46062 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-56316](https://insights.sbomify.com/CVE-2025-56316/): MCMS vulnerable SQL injection via the content_title parameter (critical 9.8)
- [CVE-2025-29287](https://insights.sbomify.com/CVE-2025-29287/): MCMS allows arbitrary file uploads in the ueditor component (critical 9.8)
- [CVE-2023-50578](https://insights.sbomify.com/CVE-2023-50578/): Mingsoft MCMS SQL injection (critical 9.8)
- [CVE-2020-20913](https://insights.sbomify.com/CVE-2020-20913/): Ming-Soft MCMS vulnerable to SQL injection (critical 9.8)
- [CVE-2022-36272](https://insights.sbomify.com/CVE-2022-36272/): Mingsoft MCMS SQL injection vulnerability in /mdiy/page/verify URI via fieldName parameter (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46062 is a high-severity path traversal vulnerability in n/a, published on 18 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-46062 in the wild and no public exploit code.

Affected packages and fixed versions:
- net.mingsoft:ms-basic (Maven): affected all versions; fixed in 2.1.16
- net.mingsoft:ms-basic (Maven): affected all versions; fixed in 2.1.16
- net.mingsoft:ms-mcms (Maven): affected all versions; fixed in 5.2.11
- net.mingsoft:ms-mcms (Maven): affected all versions; fixed in 5.2.11

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

## Sources

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

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