CVE-2020-7707: Prototype Pollution in property-expr

property-expr Updated 02 Oct 2025

Summary

06/05/2021
Yes i
Critical
9.8

CVE-2020-7707: Prototype Pollution in property-expr. Affects property-expr versions < 2.0.3. Fixed in 2.0.3. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The property-expr package is an npm package used for manipulating JavaScript object properties. It provides functions for accessing and modifying object properties using dot notation or bracket notation. The package is widely used in JavaScript applications for handling object properties. However, versions before 2.0.3 are vulnerable to Prototype Pollution, a type of vulnerability that allows an attacker to modify the prototype of an object and potentially execute arbitrary code.

Vulnerability Detail

The vulnerability in property-expr arises from a lack of proper input validation in the setter function. An attacker can craft a malicious payload that, when passed to the setter function, can modify the prototype of an object. This can lead to various security issues, such as remote code execution, privilege escalation, or denial of service. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

How To Fix

Latest published version: 2.0.6 as of 23 Oct 2026

npm install property-expr@2.0.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.0.3

This is the first release that contains the fix.

npm install property-expr@2.0.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

The property-expr package before version 2.0.3 is vulnerable to Prototype Pollution. It is crucial to update to the fixed version to mitigate the risk of potential attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for property-expr →

Share this vulnerability

FAQ

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object. By modifying the prototype, the attacker can manipulate the behavior of the object and potentially execute arbitrary code.

The consequences of this vulnerability can be severe. An attacker can exploit Prototype Pollution to execute arbitrary code, escalate privileges, or cause denial of service.

At the time of this advisory, there are no known public exploits for this vulnerability. However, it is important to update the package to the fixed version to mitigate the risk.

No, only versions before 2.0.3 are affected by this vulnerability. It is recommended to update to version 2.0.3 or later.

There are alternative packages available for manipulating object properties, such as lodash.get and dot-prop. It is recommended to evaluate these alternatives based on your specific use case and requirements.

How To Fix

Latest published version: 2.0.6 as of 23 Oct 2026

npm install property-expr@2.0.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.0.3

This is the first release that contains the fix.

npm install property-expr@2.0.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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