# CVE-2023-3990: Mingsoft MCMS HTTP POST Request search.do cross site scripting

> Remote attackers can execute arbitrary scripts via the search.do style parameter 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:** Yes
- **Published:** 28 Jul 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rxvj-5mv6-j5mc

## What is CVE-2023-3990?

CVE-2023-3990 is a low-severity cross-site scripting vulnerability in Mingsoft MCMS, published on 28 Jul 2023. 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 classified as problematic has been found in Mingsoft MCMS up to 5.3.1. This affects an unknown part of the file search.do of the component HTTP POST Request Handler. The manipulation of the argument style leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-235611.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-3990?

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

Products: Mingsoft Mcms.

## How do I fix CVE-2023-3990?

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

## Is CVE-2023-3990 being exploited?

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

Public exploit code:

- Mingsoft MCMS < 5.3.1 - Cross-Site Scripting (nuclei): http/cves/2023/CVE-2023-3990.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-2023-3990 and fix it if it is affected.

What it is: CVE-2023-3990 is a low-severity cross-site scripting vulnerability in Mingsoft MCMS, published on 28 Jul 2023. 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-2023-3990 exists.

Affected packages and fixed versions:
- net.mingsoft:ms-mcms (Maven): affected all versions; fixed in 5.3.2
- net.mingsoft:ms-mcms (Maven): affected all versions; fixed in 5.3.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-2023-3990/ (Markdown: https://insights.sbomify.com/CVE-2023-3990/index.md)
```

## Sources

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

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