Skip to content
Fencer Intel
medium 6.3

CVE-2022-4375 json

Mingsoft MCMS list sql injection

published 3y ago modified 4mo ago also GHSA-hc5g-xf64-j49j , EUVD-2022-7645

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.2%
EPSS 3.2% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known, plus a Nuclei check

Summary

A vulnerability was found in Mingsoft MCMS up to 5.2.9. It has been classified as critical. Affected is an unknown function of the file /cms/category/list. The manipulation of the argument sqlWhere leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 5.2.10 is able to address this issue. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-215196.

Patch / fix

  • maven net.mingsoft:ms-mcms 5.2.10
  • mingsoft mcms 5.2.10

Is CVE-2022-4375 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

3.15% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Mingsoft MCMS - SQL Injection nuclei detection template
  • gitee.com https://gitee.com/mingSoft/MCMS/issues/I61TG5 referenced PoC, tagged "exploit" by a source, unverified
  • vuldb.com https://vuldb.com/?id.215196 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven net.mingsoft:ms-mcms
<5.2.10
5.2.10

Affected products

  • Mingsoft MCMS

Classification

Weakness
  • CWE-707 Improper Neutralization
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.