VYPR

CWE-1321

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

VariantIncomplete

Description

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

Hierarchy (View 1000)

Parents

Children

none

Related attack patterns (CAPEC)

CAPEC-1 · CAPEC-180 · CAPEC-77

CVEs mapped to this weakness (612)

page 22 of 31
  • CVE-2021-23568HigJan 10, 2022
    risk 0.41cvss 7.3epss 0.01

    The package extend2 before 1.0.1 are vulnerable to Prototype Pollution via the extend function due to unsafe recursive merge.

  • CVE-2021-23440HigSep 12, 2021
    risk 0.41cvss 7.3epss 0.02

    This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.

  • CVE-2021-23419HigAug 8, 2021
    risk 0.41cvss 7.3epss 0.01

    This affects the package open-graph before 0.2.6. The function parse could be tricked into adding or modifying properties of Object.prototype using a __proto__ or constructor payload.

  • CVE-2021-23403HigJul 2, 2021
    risk 0.41cvss 7.3epss 0.01

    All versions of package ts-nodash are vulnerable to Prototype Pollution via the Merge() function due to lack of validation input.

  • CVE-2020-28503HigMar 23, 2021
    risk 0.41cvss 7.3epss 0.02

    The package copy-props before 2.0.5 are vulnerable to Prototype Pollution via the main functionality.

  • CVE-2020-28495HigFeb 2, 2021
    risk 0.41cvss 7.3epss 0.04

    This affects the package total.js before 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the…

  • CVE-2020-28472HigJan 19, 2021
    risk 0.41cvss 7.3epss 0.02

    This affects the package @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9; the package aws-sdk before 2.814.0. If an attacker submits a malicious INI file to an application that parses it with loadSharedConfigFiles , they will pollute the prototype on the application. This can…

  • CVE-2020-28458HigDec 16, 2020
    risk 0.41cvss 7.3epss 0.04

    All versions of package datatables.net are vulnerable to Prototype Pollution due to an incomplete fix for https://snyk.io/vuln/SNYK-JS-DATATABLESNET-598806.

  • CVE-2020-7788HigDec 11, 2020
    risk 0.41cvss 7.3epss 0.04

    This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.

  • CVE-2020-7766HigNov 10, 2020
    risk 0.41cvss 7.3epss 0.02

    This affects all versions of package json-ptr. The issue occurs in the set operation (https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does…

  • CVE-2020-7743HigOct 13, 2020
    risk 0.41cvss 7.3epss 0.04

    The package mathjs before 7.5.1 are vulnerable to Prototype Pollution via the deepExtend function that runs upon configuration updates.

  • CVE-2020-7736HigOct 2, 2020
    risk 0.41cvss 7.3epss 0.01

    The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function.

  • CVE-2020-8116HigFeb 4, 2020
    risk 0.41cvss 7.3epss 0.03

    Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.

  • CVE-2026-72769MedAug 11, 2026
    risk 0.40cvss epss 0.00

    n8n before 1.123.67, 2.31.5, and 2.32.1 contains a prototype pollution vulnerability in the VM expression engine. An authenticated user able to create or edit a workflow expression can abuse the engine's array-element access to obtain a reference to a host built-in and pollute…

  • CVE-2026-54737HigJul 31, 2026
    risk 0.40cvss 7.3epss 0.00

    @phun-ky/defaults-deep is a library like lodash defaultsDeep with array preservation and no lodash dependency. Prior to 2.0.5, defaultsDeep() recursively merges user-supplied objects without filtering proto, constructor, and prototype, allowing properties to be written to…

  • CVE-2026-46681HigJul 21, 2026
    risk 0.40cvss epss 0.00

    @nevware21/ts-utils is a comprehensive TypeScript/JavaScript utility library. Prior to version 0.14.0, the _copyProps function in lib/src/object/copy.ts uses for...in to iterate over source object properties without an Object.hasOwnProperty check, and does not filter dangerous…

  • CVE-2026-53676HigJun 17, 2026
    risk 0.40cvss 7.2epss 0.01

    ThingsBoard contains a prototype pollution vulnerability which may lead to arbitrary code execution within a sandboxed context by a user who can log in to the affected product with the tenant administrator privilege (TENANT_ADMIN).

  • CVE-2026-25754HigFeb 6, 2026
    risk 0.40cvss 7.2epss 0.00

    AdonisJS is a TypeScript-first web framework. Prior to versions 10.1.3 and 11.0.0-next.9, a prototype pollution vulnerability in AdonisJS multipart form-data parsing may allow a remote attacker to manipulate object prototypes at runtime. This issue has been patched in versions…

  • CVE-2026-23736HigJan 21, 2026
    risk 0.40cvss 7.3epss 0.00

    seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, due to improper input validation, a malicious object key can lead to prototype pollution during JSON deserialization. This vulnerability…

  • CVE-2025-13204HigNov 14, 2025
    risk 0.40cvss 7.3epss 0.00

    npm package `expr-eval` is vulnerable to Prototype Pollution. An attacker with access to express eval interface can use JavaScript prototype-based inheritance model to achieve arbitrary code execution. The npm expr-eval-fork package resolves this issue.