# CVE-2022-4350: Mingsoft MCMS search.do cross site scripting

> Remote attackers can execute arbitrary scripts via the search.do component in Mingsoft MCMS, potentially compromising user sessions.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-p46c-m4j7-mjvq

## What is CVE-2022-4350?

CVE-2022-4350 is a low-severity cross-site scripting vulnerability in Mingsoft MCMS, published on 8 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in Mingsoft MCMS 5.2.8. Affected is an unknown function of the file search.do. The manipulation of the argument content_title leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-215112.

Weakness: CWE-707 (Improper Neutralization)

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

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-4350?

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

## Is CVE-2022-4350 being exploited?

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

## 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-4350 and fix it if it is affected.

What it is: CVE-2022-4350 is a low-severity cross-site scripting vulnerability in Mingsoft MCMS, published on 8 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4350 exists.

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

## Sources

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

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