CVE-2025-32379: XSS at ctx.redirect() function in Koajs

Published Apr 9, 2025
·
Updated

### Summary In koa < 2.16.1 and < 3.0.0-alpha.5, passing untrusted user input to ctx.redirect() even after sanitizing it, may execute javascript code on the user who use the app. ### Patches This issue is patched in 2.16.1 and 3.0.0-alpha.5. ### PoC Coming soon... ### Impact 1. Redirect user to another phishing site 2. Make request to another endpoint of the application based on user's cookie 3. Steal user's cookie

Affected Software

9 affected componentsFixes available
npm/koa>=3.0.0-alpha.1<3.0.0-alpha.5
3.0.0-alpha.5
npm/koa<2.16.1
2.16.1
IBM Concert Software<=1.0.0-2.0.0
Koajs Koa Node.js<2.16.1
Koajs Koa Node.js=3.0.0-alpha0
Koajs Koa Node.js=3.0.0-alpha1
Koajs Koa Node.js=3.0.0-alpha2
Koajs Koa Node.js=3.0.0-alpha3
Koajs Koa Node.js=3.0.0-alpha4

Event History

Apr 9, 2025
Advisory Published
via GitHub·01:00 PM
CVE Published
via MITRE·03:56 PM
Data Sourced
via MITRE·03:56 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
RemedyAffected Software
Oct 28, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-32379?

CVE-2025-32379 has been classified as a high severity vulnerability due to its potential for executing malicious JavaScript code.

2

How do I fix CVE-2025-32379?

To fix CVE-2025-32379, update your koa dependency to version 2.16.1 or 3.0.0-alpha.5 or later.

3

Which versions of Koa are affected by CVE-2025-32379?

CVE-2025-32379 affects Koa versions earlier than 2.16.1 and 3.0.0-alpha.5.

4

What happens if I don't address CVE-2025-32379?

If CVE-2025-32379 is not addressed, your application may become vulnerable to cross-site scripting attacks that could compromise user data.

5

Is user input sanitization enough to mitigate CVE-2025-32379?

No, simply sanitizing user input is not sufficient to mitigate CVE-2025-32379 as the vulnerability persists even when input is sanitized.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203