How severe is CVE-2023-3990?

CVE-2023-3990 has a CVSS score of 3.5/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-3990?

CVE-2023-3990 affects the following packages: net.mingsoft:ms-mcms (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-3990?

Update net.mingsoft:ms-mcms to 5.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-3990 is resolved across your whole dependency graph.

How do I detect CVE-2023-3990 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.mingsoft:ms-mcms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-3990 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2023-3990 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-3990, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-3990?

CVE-2023-3990 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-3990?

CVE-2023-3990 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2023-3990?

A Nuclei detection template exists for CVE-2023-3990, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-3990 published, and has it been updated?

CVE-2023-3990 was published on July 28, 2023 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

CVE-2023-3990 — ms-mcms

LOW

CVE-2023-3990 is a low-severity (CVSS 3.5) Cross-site Scripting (XSS) vulnerability in net.mingsoft:ms-mcms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for net.mingsoft:ms-mcms — see the affected versions and patch details below.

Cross-site Scripting in Mingsoft MCMS

Published

Jul 28, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕net.mingsoft:ms-mcms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.mingsoft:ms-mcms`	all versions	5.3.2`net.mingsoft:ms-mcms:5.3.2`

Affected Products

1 product · 1 configurations

Application

mcmsmingsoft

≤ 5.3.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A vulnerability classified as problematic has been found in Mingsoft MCM…

gitee.comNVDAug 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.mingsoft:ms-mcms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.mingsoft:ms-mcms to 5.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-3990 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

How to detect CVE-2023-3990

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2023-3990 -u https://target

Template: Mingsoft MCMS < 5.3.1 - Cross-Site Scripting
Severity: medium
Impact: Successful exploitation could lead to unauthorized access to sensitive data.
Remediation: We recommend that you update to the latest version 5.4 or above.

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

A Cross-site Scripting vulnerability 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.

O3 Security · Impact-Aware SCA

Is CVE-2023-3990 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

OpenSSF Scorecard

Package health score

MCMS

3.4/10

Maintained10/10

Code-Review0/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jul 28, 2023

First exploit

Aug 3, 2023

6 days after disclosure — rapid exploitation

Last updated

Feb 16, 2024

Identifiers

CVE-2023-3990

References

Advisorynvd.nist.gov · CVE 2023 3990 Webgitee.com · I7K4DQ Webvuldb.com Webvuldb.com Packagegithub.com · MCMS

Related vulnerabilities

This CVE is low severity; 8 of 8 other CVEs affecting ms-mcms are rated as high or higher (top: critical).

CVE-2026-2666CVE-2025-60837CVE-2025-56316CVE-2025-29287CVE-2024-22567CVE-2023-51282CVE-2023-50578CVE-2020-22755

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024