# CVE-2020-7739: Server-side Request Forgery (SSRF)

> An attacker can craft a URL to trigger Server-Side Request Forgery in the phantomjs-seo library, potentially accessing internal resources.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j9pj-hx76-92v6, UBUNTU-CVE-2020-7739

## What is CVE-2020-7739?

CVE-2020-7739 is a high-severity server-side request forgery vulnerability in phantomjs-seo, published on 6 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects all versions of package phantomjs-seo. It is possible for an attacker to craft a url that will be passed to a PhantomJS instance allowing for an SSRF attack.

Weakness: CWE-918 (Server-Side Request Forgery)

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

2 open source packages ship an affected version, including phantomjs-seo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phantomjs-seo` | npm | All versions to 1.0.0 | None |
| `phantomjs-seo` | npm | All versions to 1.0.0 | None |

Products: Phantomjs-Seo Project Phantomjs-Seo.

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

No fix has been published for CVE-2020-7739 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7739 is a high-severity server-side request forgery vulnerability in phantomjs-seo, published on 6 Oct 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-7739 in the wild and no public exploit code.

Affected packages and fixed versions:
- phantomjs-seo (npm): affected all versions up to 1.0.0; no fix listed
- phantomjs-seo (npm): affected all versions up to 1.0.0; no fix listed

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-7739/ (Markdown: https://insights.sbomify.com/CVE-2020-7739/index.md)
```

## Sources

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

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