Skip to content

GHSA-r9wp-qq53-qvjx CVE-2026-2666

mingSoft MCMS does not properly restrict file uploads

High Maven
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
0.41%
Chance of exploitation in the next 30 days. Higher than 35.38% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
None yet
No fixed version published

Description

A flaw has been found in mingSoft MCMS 6.1.1. The affected element is an unknown function of the file /ms/file/uploadTemplate.do of the component Template Archive Handler. Executing a manipulation of the argument File can lead to unrestricted upload. The attack can be launched remotely. The exploit has been published and may be used.

Affected versions

Maven

PackageVulnerableFixed in
net.mingsoft:ms-mcms
<= 6.1.1
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
High
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
Low
Availability (vulnerable system)
Low
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Proof of concept

CVSS 3.1 4.7

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-wvv5-5g6x-hp7j
MCMS reflected cross-site scripting (XSS) vulnerability
Medium Also affects net.mingsoft:ms-mcms
GHSA-54wc-49qj-5ghj
MCMS vulnerable SQL injection via the content_title parameter
Critical Also affects net.mingsoft:ms-mcms
GHSA-3922-2r6r-r4fv
MCMS allows arbitrary file uploads in the ueditor component
Critical Also affects net.mingsoft:ms-mcms
GHSA-7qw4-9r68-2rmx
mingSoft MCMS File Upload vulnerability
High Also affects net.mingsoft:ms-mcms
GHSA-h57w-vh34-f8cw
Code injection in mingSoft MCMS
High Also affects net.mingsoft:ms-mcms
GHSA-3vvh-8c65-32j4
Mingsoft MCMS SQL injection
Critical Also affects net.mingsoft:ms-mcms
GHSA-rxvj-5mv6-j5mc
Cross-site Scripting in Mingsoft MCMS
Medium Also affects net.mingsoft:ms-mcms
GHSA-293v-5329-36wp
MCMS vulnerable to arbitrary code execution via crafted thumbnail
High Also affects net.mingsoft:ms-mcms
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor