Mversion Project maintains a focused version-management tool whose vulnerability surface centers on command-injection weaknesses, including both general command injection and OS command injection flaws in input handling. Treat this as a compact vendor profile rather than a trend line; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Mversion Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-7688HIGH The issue occurs because tagName user input is formatted inside the exec function is executed without any checks. | Jul 1, 2020 | 7.8 | 25 | NO | NO |
CVE-2020-4059HIGH In mversion before 2.0.0, there is a command injection vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untru | Jun 18, 2020 | 7.3 | 19 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Mversion Project.
Media articles that mention a CVE ID that affects a product developed by Mversion Project — matched by CVE ID, not by vendor name.