# CVE-2020-7639: eivindfjeldstad-dot contains prototype pollution vulnerability

> Prototype pollution in the eivindfjeldstad-dot library allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2020
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-wfwq-xc57-fq7v, SNYK-JS-EIVIFJDOT-564435

## What is CVE-2020-7639?

CVE-2020-7639 is a medium-severity vulnerability in @eivifj/dot, published on 6 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eivindfjeldstad-dot below 1.0.3 is vulnerable to Prototype Pollution.The function 'set' could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2020-7639?

2 open source packages ship an affected version, including @eivifj/dot. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@eivifj/dot` | npm | All versions | 1.0.3 |
| `@eivifj/dot` | npm | All versions | 1.0.3 |

Products: Dot Project Dot.

## How do I fix CVE-2020-7639?

Upgrade @eivifj/dot to 1.0.3 or later.

## Is CVE-2020-7639 being exploited?

There is no known exploitation of CVE-2020-7639 in the wild and no public exploit code.

## Other vulnerabilities in @eivifj/dot

- [CVE-2020-8141](https://insights.sbomify.com/CVE-2020-8141/): Improper Control of Generation of Code in doT (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7639 and fix it if it is affected.

What it is: CVE-2020-7639 is a medium-severity vulnerability in @eivifj/dot, published on 6 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7639 in the wild and no public exploit code.

Affected packages and fixed versions:
- @eivifj/dot (npm): affected all versions; fixed in 1.0.3
- @eivifj/dot (npm): affected all versions; fixed in 1.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7639/ (Markdown: https://insights.sbomify.com/CVE-2020-7639/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7639
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7639
- OSV: https://osv.dev/vulnerability/CVE-2020-7639

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7639/
Summaries are generated and may contain mistakes; the official description above is the record.