express vulnerable to XSS via response.redirect()
Published 10 Sept 2024 · Updated 10 Sept 2026
Is your project on an affected express?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <4.20.0
- Fixed in
- 4.20.0
npm install express@4.20.0- Affected
- >=5.0.0-alpha.1 <5.0.0
- Fixed in
- 5.0.0
npm install express@5.0.0Details
Impact
In express <4.20.0, passing untrusted user input - even after sanitizing it - to response.redirect() may execute untrusted code
Patches
this issue is patched in express 4.20.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
1. The attacker MUST control the input to response.redirect() 1. express MUST NOT redirect before the template appears 1. the browser MUST NOT complete redirection before: 1. the user MUST click on the link in the template
Is GHSA-qw6h-vgh9-j6wx in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected express, and gives you the command that fixes it.
More advisories for express
- MediumCVE-2024-10491Express ressource injection · 29 Oct 2024
- LowCVE-2024-9266Express Open Redirect vulnerability · 3 Oct 2024
- MediumCVE-2024-29041Express.js Open Redirect in malformed URLs · 25 Mar 2024
- MediumCVE-2014-6393No Charset in Content-Type Header in express · 23 Oct 2018
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.