VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

net.mingsoft:ms-mcms: vulnerability history, versions and safety

net.mingsoft:ms-mcms is a package in the Maven ecosystem. Vulert records 38 vulnerabilities for it across 43 releases, from Nov 2018 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
38 vulnerabilities recorded C20 H13 M3 L2
i
28 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 18 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all net.mingsoft:ms-mcms vulnerabilities

Vulert verdict on net.mingsoft:ms-mcms 6.2.2 i

Updated on 23 Oct 2026

Careful: 6.2.2 has 28 known vulnerabilities, and 28 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.2.2 — affected i
  • Vulnerabilities on record 38 over 7 years · 2 in the last year i
  • Latest disclosure 18 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 28 i
  • Depended on by 1 packages i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for net.mingsoft:ms-mcms, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.2.2 10 Oct 2026 C13 H11 M3 L1 non-standard No Details →
6.2.1 19 Aug 2026 C13 H11 M3 L1 non-standard No Details →
6.2.0 29 May 2026 C13 H11 M3 L1 non-standard No Details →
6.1.1 01 Dec 2025 L1 non-standard No Details →
6.1.0 27 Oct 2025 L1 non-standard No Details →
6.0.2 25 Aug 2025 L1 non-standard No Details →
6.0.1 27 Jun 2025 C1 M1 L1 non-standard No Details →
6.0.0 13 Jun 2025 C1 M1 L1 non-standard No Details →
5.5.0 23 May 2025 C1 M1 L1 non-standard No Details →
5.4.5 03 Apr 2025 M1 L1 Apache-2.0 No Details →
5.4.4 27 Feb 2025 M1 L1 Apache-2.0 No Details →
5.4.3 28 Dec 2024 C1 M1 L1 Apache-2.0 No Details →
5.4.2 28 Sep 2024 C1 M1 L1 Apache-2.0 No Details →
5.4.1 29 Jul 2024 C1 M1 L1 Apache-2.0 No Details →
5.4.0 29 Apr 2024 C1 M1 L1 Apache-2.0 No Details →
5.3.6 04 Feb 2024 C1 M1 L1 Apache-2.0 No Details →
5.3.5 16 Nov 2023 C1 H1 M1 L1 Apache-2.0 No Details →
5.3.4 28 Sep 2023 C1 H1 M1 L1 Apache-2.0 No Details →
5.3.3 04 Aug 2023 C1 H1 M1 L1 Apache-2.0 No Details →
5.3.2 29 Jun 2023 C1 H1 M1 L1 Apache-2.0 No Details →
5.3.1 31 Mar 2023 C1 H1 M1 L2 Apache-2.0 No Details →
5.3.0 28 Jan 2023 C1 H1 M1 L2 Apache-2.0 No Details →
5.2.11 16 Dec 2022 C1 H1 M1 L2 Apache-2.0 No Details →
5.2.10 14 Nov 2022 C1 H2 M1 L2 Apache-2.0 No Details →
5.2.9 09 Sep 2022 C2 H3 M2 L2 Apache-2.0 No Details →
5.2.8 07 May 2022 C6 H3 M3 L2 Apache-2.0 No Details →
5.2.7 01 Mar 2022 C6 H6 M3 L2 Apache-2.0 No Details →
5.2.6 07 Feb 2022 C6 H6 M3 L2 Apache-2.0 No Details →
5.2.5 28 Dec 2021 C11 H8 M3 L2 Apache-2.0 No Details →
5.2.4 29 Sep 2021 C14 H10 M3 L2 Apache-2.0 No Details →
5.2.3 08 Aug 2021 C14 H10 M3 L2 Apache-2.0 No Details →
5.2.2 11 Jun 2021 C14 H10 M3 L2 Apache-2.0 No Details →
5.2.1 14 May 2021 C14 H10 M3 L2 Apache-2.0 No Details →
5.2.0.RELEASE 07 Jan 2021 C14 H10 M3 L2 Apache-2.0 No Details →
5.2.0 05 Dec 2020 C14 H10 M3 L2 Apache-2.0 No Details →
5.2 04 Dec 2020 C14 H10 M3 L2 Apache-2.0 No Details →
5.1 16 Sep 2020 C15 H10 M3 L2 non-standard No Details →
5.0.1 17 Jun 2020 C17 H10 M3 L2 non-standard No Details →
5.0.0 11 Jan 2020 C17 H11 M3 L2 non-standard No Details →
4.7.2 04 Nov 2019 C17 H11 M3 L2 non-standard No Details →
4.7.1 25 Aug 2019 C17 H11 M3 L2 non-standard No Details →
4.6.5 01 Aug 2018 C18 H13 M3 L2 non-standard No Details →
4.6.3-SNAPSHOTS 11 May 2018 C18 H13 M3 L2 non-standard No Details →

All 43 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2022 25
  • 2023 5
  • 2024 2
  • 2025 3
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 38 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for net.mingsoft:ms-mcms

The 5 most severe of 38 vulnerabilities recorded for this package

Search all 38 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-44868: SQL Injection in ming-soft MCMS v5.1 9.8 critical No fix published 18 Feb 2022
CVE-2025-29287: MCMS Arbitrary File Upload Vulnerability in ueditor Component 9.8 critical 5.4.4 21 Apr 2025
CVE-2021-46386: Mingsoft MCMS Remote Code Execution via File Upload 9.8 critical No fix published 27 Jan 2022
CVE-2022-4375: SQL Injection Vulnerability in Mingsoft MCMS 9.8 critical 5.2.10 09 Dec 2022
CVE-2022-36599: SQL Injection Vulnerability in Mingsoft MCMS 9.8 critical No fix published 17 Aug 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About net.mingsoft:ms-mcms

Is net.mingsoft:ms-mcms safe to use?

Vulert records 38 vulnerabilities for net.mingsoft:ms-mcms in Maven: 20 critical, 13 high, 3 medium and 2 low. 28 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is net.mingsoft:ms-mcms's Vulert package health score?

Vulert scores net.mingsoft:ms-mcms 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of net.mingsoft:ms-mcms affected?

Yes. 6.2.2, the version you would install today, has 28 known vulnerabilities, and 28 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of net.mingsoft:ms-mcms should I use?

6.2.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does net.mingsoft:ms-mcms have?

38 vulnerabilities are recorded for net.mingsoft:ms-mcms in the Maven ecosystem: 20 critical, 13 high, 3 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new net.mingsoft:ms-mcms vulnerabilities disclosed?

2 vulnerabilities were recorded for net.mingsoft:ms-mcms in the last 12 months, and the oldest entry in this database dates to 01 Nov 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of net.mingsoft:ms-mcms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor net.mingsoft:ms-mcms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the net.mingsoft:ms-mcms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.