Path traversal in MCMS

published 2022-02-18 4y ago modified 2026-06-17 4mo ago also GHSA-73wx-rpj3-mx46 , EUVD-2022-0878

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits: 0; none known

MCMS v5.2.4 was discovered to contain an arbitrary file deletion vulnerability via the component /template/unzip.do.

Is CVE-2021-46037 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.03% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

lycshub.github.io https://lycshub.github.io/2021/12/28/MCMS-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:N/I:P/A:P
GitHub	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	net.mingsoft:ms-mcms	<=5.2.4	no fix listed

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

lycshub.github.io /2021/12/28/MCMS-vulnerabilities/
exploit, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2021-46037
advisory
lycshub.github.io /2021/12/28/MCMS-vulnerabilities
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.