Skip to content

Product

openjsf express vulnerabilities

5 published CVES affecting openjsf express, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
5
Critical
0
High
1
Medium
4
Low
0
Unscored
0
CISA KEV
0

Latest openjsf express CVEs

Newest publication first

  1. CVE-2024-10491 Preload arbitrary resources by injecting additional `Link` headers

    Published
    MediumCVSS 5.3 EPSS 0.44%

    A vulnerability has been identified in the Express response.links function, allowing for arbitrary resource injection in the Link header when unsanitized data is used. The issue arises from improper sanitization in Link header values, which can allow a combination of characters l...

  2. CVE-2024-43796 express vulnerable to XSS via response.redirect()

    Published
    MediumCVSS 4.7 EPSS 0.49%

    Express.js minimalist web framework for node. In express < 4.20.0, passing untrusted user input - even after sanitizing it - to response.redirect() may execute untrusted code. This issue is patched in express 4.20.0.

  3. CVE-2024-29041 Express.js Open Redirect in malformed URLs

    Published
    MediumCVSS 6.1 EPSS 0.79%

    Express.js minimalist web framework for node. Versions of Express.js prior to 4.19.0 and all pre-release alpha and beta versions of 5.0 are affected by an open redirect vulnerability using malformed URLs. When a user of Express performs a redirect using a user-provided URL Expres...

  4. CVE-2022-24999 qs vulnerable to Prototype Pollution

    Published
    HighCVSS 7.5 EPSS 15.7% PoC

    qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payloa...

  5. CVE-2014-6393 No Charset in Content-Type Header in express

    Published
    MediumCVSS 6.1 EPSS 1.1%

    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.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.