CVE-2014-6393
N/A
Published: August 9, 2017 at 06:00 PM UTC
Updated: June 17, 2026 at 12:13 AM UTC
1 product affected across 1 vendorExpress
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 1%
Description
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.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.
References (2)
x_refsource_CONFIRMIssue TrackingThird Party AdvisoryVDB Entry
Source: [email protected]
https://bugzilla.redhat.com/show_bug.cgi?id=1203190x_refsource_CONFIRMThird Party Advisory
Source: [email protected]
https://nodesecurity.io/advisories/express-no-charset-in-content-type-headerQuick Info
StatusMODIFIED
CWE
CWE-79
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card