# CVE-2022-4375: Mingsoft MCMS list sql injection

> Remote attackers can exploit SQL injection in Mingsoft MCMS to read or modify database contents via the category list endpoint.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-hc5g-xf64-j49j

## What is CVE-2022-4375?

CVE-2022-4375 is a medium-severity SQL injection vulnerability in Mingsoft MCMS, published on 9 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Mingsoft MCMS up to 5.2.9. It has been classified as critical. Affected is an unknown function of the file /cms/category/list. The manipulation of the argument sqlWhere leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 5.2.10 is able to address this issue. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-215196.

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

## Which versions are affected by CVE-2022-4375?

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 | All versions | 5.2.10 |
| `net.mingsoft:ms-mcms` | Maven | All versions | 5.2.10 |

Products: Mingsoft Mcms.

## How do I fix CVE-2022-4375?

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

## Is CVE-2022-4375 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4375 exists.

Public exploit code:

- Mingsoft MCMS - SQL Injection (nuclei): http/cves/2022/CVE-2022-4375.yaml

## Other vulnerabilities in Mingsoft MCMS

- [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-2022-4375 and fix it if it is affected.

What it is: CVE-2022-4375 is a medium-severity SQL injection vulnerability in Mingsoft MCMS, published on 9 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4375 exists.

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

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

## Sources

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

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