VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mootools: vulnerability history, versions and safety

mootools is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 12 releases, from Sep 2021 to Jan 2023. 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
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 mootools vulnerabilities

Vulert verdict on mootools 1.5.2 i

Updated on 23 Oct 2026

Careful: 1.5.2 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 45/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.5.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 03 Jan 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Depended on by 53 packages i
  • Stars 23 i
  • OpenSSF scorecard 0/10 i
  • Last release 133 months ago 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 mootools, 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
1.5.2 20 Sep 2015 H1 M1 — No Details →
1.5.1-2 02 Mar 2015 H1 M1 — No Details →
1.5.1-1 02 Mar 2015 H1 M1 — No Details →
1.5.1 30 Aug 2014 H1 M1 — No Details →
1.4.5-2 07 May 2013 H1 M1 — No Details →
1.4.5-1 06 May 2013 H1 M1 — No Details →
1.4.5 01 Aug 2012 H1 M1 — No Details →
1.4.4 23 Feb 2012 H1 M1 — No Details →
1.3.2 29 Apr 2011 H1 M1 — No Details →
1.3.1-2 03 Apr 2011 H1 M1 — No Details →
1.3.1-1 01 Apr 2011 H1 M1 — No Details →
1.3.1 28 Mar 2011 H1 M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2023 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 mootools

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
MooTools Regular Expression Denial of Service in mootools 7.5 high No fix published 03 Jan 2023
CVE-2021-23432: Prototype Pollution in mootools 5.4 medium No fix published 02 Sep 2021

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 mootools

Is mootools safe to use?

Vulert records 2 vulnerabilities for mootools in npm: 0 critical, 1 high, 1 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is mootools's Vulert package health score?

Vulert scores mootools 45/100, which reads as risky. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of mootools affected?

Yes. 1.5.2, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of mootools should I use?

1.5.2 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 mootools have?

2 vulnerabilities are recorded for mootools 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 mootools vulnerabilities disclosed?

0 vulnerabilities were recorded for mootools in the last 12 months, and the oldest entry in this database dates to 02 Sep 2021. 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 mootools 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 mootools for upcoming vulnerabilities?

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