# CVE-2022-36272: Mingsoft MCMS SQL injection vulnerability in /mdiy/page/verify URI via fieldName parameter

> SQL injection in Mingsoft MCMS allows attackers to manipulate database queries via the fieldName parameter, potentially exposing or altering data.

- **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:** No
- **Published:** 16 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hmj3-mqgw-2fq6

## What is CVE-2022-36272?

CVE-2022-36272 is a critical SQL injection vulnerability in n/a, published on 16 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mingsoft MCMS 5.2.8 was discovered to contain a SQL injection vulnerability in /mdiy/page/verify URI via fieldName parameter.

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

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

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

Products: Mingsoft Mcms.

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

No fix has been published for CVE-2022-36272 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-36272 being exploited?

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

## Other vulnerabilities in n/a

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

What it is: CVE-2022-36272 is a critical SQL injection vulnerability in n/a, published on 16 Aug 2022. 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-2022-36272 in the wild and no public exploit code.

Affected packages and fixed versions:
- net.mingsoft:ms-mcms (Maven): affected all versions up to 5.2.8; no fix listed
- net.mingsoft:ms-mcms (Maven): affected all versions up to 5.2.8; no fix listed

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

## Sources

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

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