CVE-2014-6393: No Charset in Content-Type Header in express

express Updated 02 Oct 2025

Summary

23/10/2018
Yes i
Moderate
6.1

CVE-2014-6393: No Charset in Content-Type Header in express. Affects express across 2 version ranges.

< 3.11.0 >= 4.0.0, < 4.5.0

Fixed in 3.11.0 or 4.5.0, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2014-6393 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

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

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Express is a popular web application framework for Node.js that simplifies the process of building web applications. It provides a robust set of features and middleware for creating APIs, handling routes, and managing HTTP requests and responses. However, vulnerable versions of express do not specify a charset field in the content-type header while displaying 400 level response messages.

Vulnerability Detail

The lack of enforcing the user's browser to set the correct charset can be exploited by an attacker to perform a cross-site scripting attack using non-standard encodings like UTF-7. This vulnerability allows an attacker to inject malicious scripts into the web application, potentially leading to unauthorized access, data theft, or other malicious activities.

How To Fix

Fixed versions by release line

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

  • < 3.11.0 3.11.0
    npm install express@3.11.0
  • >= 4.0.0, < 4.5.0 4.5.0
    npm install express@4.5.0

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 specific workaround mentioned for this vulnerability.

Conclusion

In conclusion, the lack of charset specification in the content-type header of vulnerable versions of express can lead to cross-site scripting attacks. It is crucial to update express to the recommended fixed versions to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for express →

Share this vulnerability

FAQ

This vulnerability allows an attacker to perform cross-site scripting attacks, potentially leading to unauthorized access, data theft, or other malicious activities.

Vulnerable versions of express include 0.0.1 to 3.10.x for express 3.x, and 4.0.0 to 4.4.x for express 4.x.

There are known exploits for cross-site scripting vulnerabilities in general, but there is no specific information available regarding exploits targeting this vulnerability in express.

The recommended mitigation is to update express to the fixed versions mentioned above.

Yes, the CVSS score for this vulnerability is 6.1 (Moderate).

Related vulnerabilities

Recent vulnerabilities recorded for express.

How To Fix

Fixed versions by release line

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

  • < 3.11.0 3.11.0
    npm install express@3.11.0
  • >= 4.0.0, < 4.5.0 4.5.0
    npm install express@4.5.0

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