Open Redirect Vulnerability in ecstatic

ecstatic Updated 02 Oct 2025

Summary

19/08/2020
MODERATE
Yes i
Moderate
Not published

GHSA-x4rf-4mqf-cm8w: Open Redirect in ecstatic. Affects ecstatic across 3 version ranges.

< 2.2.2 >= 3.0.0, < 3.3.2 >= 4.0.0, < 4.1.2

Fixed in 2.2.2, 3.3.2 or 4.1.2, depending on the release line you run. 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

ecstatic is an npm package that provides a simple static file server for Node.js. It is commonly used to serve static assets such as HTML, CSS, and JavaScript files. The package allows developers to quickly set up a server to host their static files. However, ecstatic is vulnerable to an open redirect vulnerability.

Vulnerability Detail

The open redirect vulnerability in ecstatic allows an attacker to redirect users to a malicious website of their choice. This can be exploited by crafting a specially crafted URL that tricks the server into redirecting the user to the attacker's website. The impact of this vulnerability can range from phishing attacks to spreading malware or stealing sensitive information.

How To Fix

Latest published version: 4.1.4 as of 22 Oct 2026

npm install ecstatic@4.1.4

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

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 2.2.2 2.2.2
    npm install ecstatic@2.2.2
  • >= 3.0.0, < 3.3.2 3.3.2
    npm install ecstatic@3.3.2
  • >= 4.0.0, < 4.1.2 4.1.2
    npm install ecstatic@4.1.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to update the package to the latest version as soon as possible.

Conclusion

The open redirect vulnerability in ecstatic can have serious security implications. It is crucial for developers to update the package to the latest version to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ecstatic →

Share this vulnerability

FAQ

An open redirect vulnerability is a security flaw that allows an attacker to redirect users to a malicious website.

An attacker can use an open redirect vulnerability to trick users into visiting a malicious website, which can lead to phishing attacks, spreading malware, or stealing sensitive information.

To fix the open redirect vulnerability in ecstatic, you should update the package to the latest version available. For versions 0.x.x, update to version 2.2.2. For versions 3.x.x, update to version 3.3.2. For versions 4.x.x, update to version 4.1.2.

There is no known workaround for this vulnerability. It is recommended to update the package to the latest version.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file and Vulert will analyze it for open-source vulnerabilities in real-time.

Related vulnerabilities

Recent vulnerabilities recorded for ecstatic.

How To Fix

Latest published version: 4.1.4 as of 22 Oct 2026

npm install ecstatic@4.1.4

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

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 2.2.2 2.2.2
    npm install ecstatic@2.2.2
  • >= 3.0.0, < 3.3.2 3.3.2
    npm install ecstatic@3.3.2
  • >= 4.0.0, < 4.1.2 4.1.2
    npm install ecstatic@4.1.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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