CVE-2014-6393 json
No Charset in Content-Type Header in express
published 2017-08-09 9 y ago modified 2026-06-17 4 mo ago also GHSA-gpvr-g6gh-9mc2 , EUVD-2018-0603
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm express 3.11.0, 4.5.0
- node-express Debian 14, Debian 13, Debian 12 4.16.4-1
debian advisories DEBIAN-CVE-2014-6393
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-6393 updated cvss 4.3
express: cross-site scripting via content-type header
-
Red Hat OpenShift Enterprise 2 nodejs010-nodejs-expressaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | express | <3.11.0 >=4.0.0, <4.5.0 |
3.11.0 4.5.0 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
nodesecurity.io
/advisories/express-no-charset-in-content-type-header
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1203190
web, issue-tracking, third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2014-6393
advisory
-
github.com
/advisories/GHSA-gpvr-g6gh-9mc2
advisory
-
npmjs.com
/advisories/8
web
Sources
- CVE List CVE-2014-6393
- GitHub Advisory GHSA-gpvr-g6gh-9mc2
- NVD CVE-2014-6393
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.