Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2022-4640

LOW

CVE-2022-4640 is a low-severity (CVSS 3.5) CWE-707 vulnerability in net.mingsoft:ms-mcms. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-4640 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mingsoft MCMS Article save cross site scripting

Also known asGHSA-6rvv-h8g7-728w
Published
Dec 21, 2022
Updated
Jul 15, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known

Blast Radius

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 has been found in Mingsoft MCMS 5.2.9 and classified as problematic. Affected by this vulnerability is the function save of the component Article Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216499.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
Mavennet.mingsoft:ms-mcmsall versionsNo fix
Exploits & PoCs
1

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 dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.mingsoft:ms-mcms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of net.mingsoft:ms-mcms has shipped for CVE-2022-4640 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-4640 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-4640. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability has been found in Mingsoft MCMS 5.2.9 and classified as problematic. Affected by this vulnerability is the function save of the component Article Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216499.
O3 Security · Impact-Aware SCA

Is CVE-2022-4640 in your dependencies?

O3 detects CVE-2022-4640 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.