CVE-2021-20085: Prototype Pollution in backbone-query-parameters

backbone-query-parameters Updated 02 Oct 2025

Summary

06/05/2021
No i
High
8.8

CVE-2021-20085: Prototype Pollution in backbone-query-parameters. Affects backbone-query-parameters versions < 0.4.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

backbone-query-parameters is an npm package that provides functionality for managing query parameters in Backbone.js applications. It allows users to easily manipulate and retrieve query parameters from the URL. However, version 0.4.0 of backbone-query-parameters is vulnerable to Prototype Pollution, a type of vulnerability where an attacker can inject properties into Object.prototype. This can lead to various security issues and unexpected behavior in applications that use this package.

Vulnerability Detail

The vulnerability in backbone-query-parameters arises from improper control over the modification of Object Prototype Attributes, also known as Prototype Pollution. An attacker can exploit this vulnerability to inject malicious properties into Object.prototype, which can then be accessed and manipulated by other parts of the application. This can result in a range of security issues, including remote code execution, information disclosure, and denial of service attacks. The severity of this vulnerability is rated as HIGH with a CVSS score of 8.8.

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

There is no known workaround for this vulnerability. It is essential to upgrade to a non-vulnerable version of backbone-query-parameters to mitigate the risk.

Conclusion

The Prototype Pollution vulnerability in backbone-query-parameters can have severe consequences for applications that use this package. It is crucial to upgrade to a non-vulnerable version, starting from version 0.4.0. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for backbone-query-parameters →

Share this vulnerability

FAQ

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior and security issues in the application.

An attacker can exploit this vulnerability by injecting malicious properties into Object.prototype, which can then be accessed and manipulated by other parts of the application.

The consequences of this vulnerability can vary depending on how it is exploited. Possible outcomes include remote code execution, information disclosure, and denial of service attacks.

Yes, upgrading to a version of backbone-query-parameters that is not affected by this vulnerability will fix the issue.

No, there are no known workarounds for this vulnerability. Upgrading to a non-vulnerable version is the recommended solution.

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