# CVE-2025-56316: MCMS vulnerable SQL injection via the content_title parameter

> Remote attackers can execute arbitrary SQL queries via the content_title parameter in MCMS, potentially accessing or modifying database content.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** GHSA-54wc-49qj-5ghj

## What is CVE-2025-56316?

CVE-2025-56316 is a critical SQL injection vulnerability in n/a, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL injection vulnerability in the content_title parameter of the /cms/content/list endpoint in MCMS 5.5.0 allows remote attackers to execute arbitrary SQL queries via unsanitized input in the FreeMarker template rendering.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-56316?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net.mingsoft:ms-mcms` | Maven | From 5.5.0 | 6.0.2 |
| `net.mingsoft:ms-mcms` | Maven | From 5.5.0 | 6.0.2 |

Products: Mingsoft Mcms.

## How do I fix CVE-2025-56316?

Upgrade net.mingsoft:ms-mcms to 6.0.2 or later.

## Is CVE-2025-56316 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2022-36599](https://insights.sbomify.com/CVE-2022-36599/): Mingsoft MCMS SQL injection vulnerability in /mdiy/model/delete URI via models List (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56316 and fix it if it is affected.

What it is: CVE-2025-56316 is a critical SQL injection vulnerability in n/a, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-56316 in the wild and no public exploit code.

Affected packages and fixed versions:
- net.mingsoft:ms-mcms (Maven): affected from 5.5.0; fixed in 6.0.2
- net.mingsoft:ms-mcms (Maven): affected from 5.5.0; fixed in 6.0.2

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

## Sources

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

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