CVE-2021-23432: Prototype Pollution in mootools

mootools Updated 02 Oct 2025

Summary

02/09/2021
No i
Moderate
5.4

CVE-2021-23432: Prototype Pollution in mootools. Affects mootools versions < 1.5.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Mootools is an open-source JavaScript framework that provides a set of utilities for building interactive web applications. It offers a range of features such as DOM manipulation, event handling, and AJAX functionality. The package is widely used in web development projects and has versions available for the npm ecosystem. However, all versions of the mootools package are vulnerable to prototype pollution due to the ability to pass untrusted input to the Object.merge() function.

Vulnerability Detail

The vulnerability in mootools arises from the Object.merge() function's lack of input validation, allowing untrusted input to modify the prototype of objects. This can lead to prototype pollution, where an attacker can inject or modify properties on Object.prototype, potentially leading to various security issues. The impact of this vulnerability can range from data integrity and confidentiality breaches to remote code execution.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, developers can implement input validation and sanitization before passing data to the Object.merge() function. By ensuring that only trusted input is processed, the risk of prototype pollution can be mitigated. Here's an example of how input validation can be implemented in JavaScript:

function mergeObjects(target, source) {
  if (typeof target !== 'object' || typeof source !== 'object') {
    throw new Error('Invalid input');
  }

  return Object.assign(target, source);
}

Conclusion

In conclusion, the mootools package is vulnerable to prototype pollution due to the lack of input validation in the Object.merge() function. This can have serious security implications, including data integrity and confidentiality breaches. It is crucial for developers to update to a secure version of the package that includes a fix for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for mootools →

Share this vulnerability

FAQ

Prototype pollution is a vulnerability that occurs when untrusted data is able to modify the prototype of objects. This can lead to unexpected behavior and security issues.

Object.merge() is a function in mootools that allows merging properties from multiple objects into a single object. However, it is vulnerable to prototype pollution when untrusted input is passed to it.

The consequences of this vulnerability can include data integrity and confidentiality breaches, remote code execution, and unexpected behavior in the application.

Yes, all versions of the mootools package are affected by this vulnerability. Developers should update to a secure version that includes a fix for the prototype pollution issue.

To update the mootools package, you can use the package manager command 'npm update mootools'. Make sure to review the release notes and changelog to identify the fixed version.

Related vulnerabilities

Recent vulnerabilities recorded for mootools.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

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 →
Help improve this record
Report an issue or send feedback