VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mversion: vulnerability history, versions and safety

mversion is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 34 releases, from Jun 2020 to May 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mversion vulnerabilities

Vulert verdict on mversion 2.0.1 i

Updated on 23 Oct 2026

Good news: 2.0.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 50/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on 2.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.0.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2021 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i
  • Stars 202 i
  • OpenSSF scorecard 1/10 i
  • Last release 75 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for mversion, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.1 30 Jun 2020 none MIT — Details →
2.0.0 15 Jun 2020 M1 MIT Yes Details →
1.13.0 08 Feb 2019 H1 M1 MIT Yes Details →
1.12.0 23 Jun 2018 H1 M1 MIT Yes Details →
1.10.1 26 Aug 2015 H1 M1 MIT Yes Details →
1.10.0 09 Mar 2015 H1 M1 MIT Yes Details →
1.9.0 15 Dec 2014 H1 M1 MIT Yes Details →
1.8.0 09 Nov 2014 H1 M1 MIT Yes Details →
1.7.0 02 Nov 2014 H1 M1 MIT Yes Details →
1.6.1 08 Oct 2014 H1 M1 MIT Yes Details →
1.6.0 03 Oct 2014 H1 M1 MIT Yes Details →
1.5.0 02 Oct 2014 H1 M1 MIT Yes Details →
1.4.0 02 Oct 2014 H1 M1 MIT Yes Details →
1.3.0 04 Aug 2014 H1 M1 MIT Yes Details →
1.2.0 25 Jul 2014 H1 M1 MIT Yes Details →
1.1.0 24 Jul 2014 H1 M1 MIT Yes Details →
1.0.0 06 Jul 2014 H1 M1 MIT Yes Details →
0.5.1 06 Jul 2014 H1 M1 MIT Yes Details →
0.5.0 06 Jul 2014 H1 M1 MIT Yes Details →
0.4.3 03 Apr 2014 H1 M1 MIT Yes Details →
0.4.2 25 Mar 2014 H1 M1 MIT Yes Details →
0.4.1 02 Mar 2014 H1 M1 MIT Yes Details →
0.3.1 10 Feb 2014 H1 M1 MIT Yes Details →
0.3.0 19 Jan 2014 H1 M1 MIT Yes Details →
0.2.3 19 Jan 2014 H1 M1 MIT Yes Details →
0.2.2 05 Nov 2013 H1 M1 MIT Yes Details →
0.2.1 01 Nov 2013 H1 M1 MIT Yes Details →
0.2.0 15 May 2013 H1 M1 MIT Yes Details →
0.1.3 13 May 2013 H1 M1 MIT Yes Details →
0.1.2 02 May 2013 H1 M1 MIT Yes Details →
0.1.1 02 May 2013 H1 M1 MIT Yes Details →
0.1.0 02 May 2013 H1 M1 MIT Yes Details →
0.0.5 30 Apr 2013 H1 M1 MIT Yes Details →
0.0.4 30 Apr 2013 H1 M1 MIT Yes Details →
0.0.1 30 Apr 2013 H1 M1 MIT Yes Details →

All 35 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mversion

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2020-7688: OS Command Injection in mversion 7.8 medium 2.0.1 17 May 2021
CVE-2020-4059: Command injection in mversion 7.3 high 2.0.0 18 Jun 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mversion

Is mversion safe to use?

Vulert records 2 vulnerabilities for mversion in npm: 0 critical, 1 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is mversion's Vulert package health score?

Vulert scores mversion 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of mversion affected?

No. 2.0.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of mversion should I use?

2.0.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mversion have?

2 vulnerabilities are recorded for mversion in the npm ecosystem: 0 critical, 1 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mversion vulnerabilities disclosed?

0 vulnerabilities were recorded for mversion in the last 12 months, and the oldest entry in this database dates to 18 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mversion are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mversion for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mversion version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.