CVE-2023-3990 — ms-mcms
LOWCVE-2023-3990 is a low-severity (CVSS 3.5) Cross-site Scripting (XSS) vulnerability in net.mingsoft:ms-mcms. 1 public exploit reference exists, 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
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-3990 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
net.mingsoft:ms-mcmsReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.mingsoft:ms-mcms | all versions | 5.3.2net.mingsoft:ms-mcms:5.3.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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 O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-3990 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-3990. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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
Is CVE-2023-3990 in your dependencies?
O3 Security finds CVE-2023-3990 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.