CVE-2020-7739: Server-Side Request Forgery in phantomjs-seo

phantomjs-seo Updated 02 Oct 2025

Summary

10/05/2021
No i
High
8.2

CVE-2020-7739: Server-Side Request Forgery in phantomjs-seo. Affects phantomjs-seo versions < 1.0.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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The phantomjs-seo package is an npm package used for search engine optimization (SEO) purposes. It provides a PhantomJS instance that can be used to render web pages and extract SEO-related information. The package allows users to generate screenshots, PDFs, and other SEO-related data. However, all versions of the package are vulnerable to a Server-Side Request Forgery (SSRF) attack.

Vulnerability Detail

The vulnerability in phantomjs-seo allows an attacker to craft a URL that will be passed to a PhantomJS instance, leading to an SSRF attack. This means that an attacker can make the PhantomJS instance send arbitrary requests to internal resources or external systems, potentially bypassing security measures and accessing sensitive information. The vulnerability has a CVSS score of 8.2, indicating a high severity level.

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

As a temporary workaround, it is advised to avoid using the phantomjs-seo package until a fixed version is available. Alternatively, developers can implement input validation and sanitization to prevent malicious URLs from being passed to the PhantomJS instance.

Conclusion

The phantomjs-seo package is vulnerable to a Server-Side Request Forgery (SSRF) attack. It is recommended to update the package to a version that is not affected by the vulnerability or implement input validation and sanitization to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for phantomjs-seo →

Share this vulnerability

FAQ

phantomjs-seo is an npm package used for search engine optimization (SEO) purposes. It provides a PhantomJS instance for rendering web pages and extracting SEO-related information.

Server-Side Request Forgery (SSRF) is a vulnerability that allows an attacker to make a server-side application send arbitrary requests to internal resources or external systems.

The SSRF vulnerability in phantomjs-seo can allow an attacker to bypass security measures and access sensitive information. It can also be used to perform attacks on internal systems or to scan for open ports.

To fix this vulnerability, update the phantomjs-seo package to a version that is not affected by the SSRF vulnerability. Alternatively, implement input validation and sanitization to prevent malicious URLs from being passed to the PhantomJS instance.

As a temporary workaround, avoid using the phantomjs-seo package until a fixed version is available. Additionally, implement input validation and sanitization to mitigate the risk of SSRF attacks.

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