CWE
79
Advisory Published
CVE Published
Updated

CVE-2014-6393: XSS

First published: Wed Mar 18 2015(Updated: )

The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/express<3.11
3.11
redhat/express<4.5
4.5
Node.js Express<=3.10.5
Node.js Express=4.0.0
Node.js Express=4.1.0
Node.js Express=4.1.1
Node.js Express=4.1.2
Node.js Express=4.2.0
Node.js Express=4.3.0
Node.js Express=4.3.1
Node.js Express=4.3.2
Node.js Express=4.4.0
Node.js Express=4.4.1
Node.js Express=4.4.2
Node.js Express=4.4.3
Node.js Express=4.4.4
Node.js Express=4.4.5

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2014-6393?

    CVE-2014-6393 is considered a high severity vulnerability that may allow remote XSS attacks due to improper handling of the Content-Type header.

  • How do I fix CVE-2014-6393?

    To fix CVE-2014-6393, upgrade the Express framework to version 3.11 or 4.5 or later.

  • Which versions of Express are affected by CVE-2014-6393?

    CVE-2014-6393 affects Express versions prior to 3.11 and any version before 4.5.

  • Can CVE-2014-6393 lead to successful XSS attacks?

    Yes, CVE-2014-6393 can allow attackers to conduct XSS attacks through non-standard encoding if exploited.

  • Is CVE-2014-6393 specific to Node.js applications?

    Yes, CVE-2014-6393 specifically affects the Express web framework used in Node.js applications.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203