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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.1, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 1 product from openjsf organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-08-09T18:29:00.480
2025-04-20T01:37:25.860
Deferred
CVSSv3.0: 6.1 (MEDIUM)
AV:N/AC:M/Au:N/C:N/I:P/A:N
8.6
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | openjsf | express | ≤ 3.10.5 | Yes |
| Application | openjsf | express | 4.0.0 | Yes |
| Application | openjsf | express | 4.1.0 | Yes |
| Application | openjsf | express | 4.1.1 | Yes |
| Application | openjsf | express | 4.1.2 | Yes |
| Application | openjsf | express | 4.2.0 | Yes |
| Application | openjsf | express | 4.3.0 | Yes |
| Application | openjsf | express | 4.3.1 | Yes |
| Application | openjsf | express | 4.3.2 | Yes |
| Application | openjsf | express | 4.4.0 | Yes |
| Application | openjsf | express | 4.4.1 | Yes |
| Application | openjsf | express | 4.4.2 | Yes |
| Application | openjsf | express | 4.4.3 | Yes |
| Application | openjsf | express | 4.4.4 | Yes |
| Application | openjsf | express | 4.4.5 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For openjsf's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.