Potential SQL Injection in sequelize
Affected versions of sequelize are vulnerable to SQL Injection when user input is passed into findOne or into a statement such as where: "user input".
Recommendation
Update to version 3.0.0 or later.
Version 3.0.0 will introduce a number of breaking changes. Thankfully, the project authors have provided a 2.x -> 3.x upgrade guide to ease this transition.
If upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of where: "input" and findOne("input") are properly sanitized, such as by the use of a wrapper function.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | sequelize | < 3.0.0 | 3.0.0 |
References
- Weakness (CWE)
CWE-89- Platform
- npm
- Package
sequelize- Disclosed
- 18.02.2019
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-2v7q-2xqx-f4q5 - CC BY 4.0
Vulnerability history: sequelize
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 18
- First → latest
- 10.2017 08.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 8
- High 7
- Medium 3
Disclosures per year
- 2017: 1
- 2018: 0
- 2019: 9
- 2020: 2
- 2021: 0
- 2022: 0
- 2023: 4
- 2024: 0
- 2025: 0
- 2026: 2
-
Potential SQL Injection in sequelize this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.