CVE-2016-10553: Potential SQL Injection in sequelize

sequelize Updated 02 Oct 2025

Summary

18/02/2019
Yes i
High
Not published

CVE-2016-10553: Potential SQL Injection in sequelize. Affects sequelize versions < 3.0.0. Fixed in 3.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Sequelize is an Object-Relational Mapping (ORM) library for Node.js that provides easy access to databases by mapping database entries to objects. It is widely used for managing SQL databases in Node.js applications. However, versions of Sequelize prior to 3.0.0 are vulnerable to SQL Injection when user input is passed into the findOne method or used in a statement like where: "user input".

Vulnerability Detail

The vulnerability arises due to inadequate input sanitization, allowing an attacker to manipulate the SQL queries executed by Sequelize. By injecting malicious SQL code, an attacker can bypass authentication, access unauthorized data, modify the database, or even execute arbitrary commands on the underlying system. This vulnerability poses a high risk to the confidentiality, integrity, and availability of the affected application and its data.

How To Fix

Minimum fixed version

3.0.0

This is the first release that contains the fix.

npm install sequelize@3.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading is not possible, a temporary workaround is to sanitize user input before passing it to the vulnerable functions. This can be achieved by using a wrapper function that applies proper input validation and sanitization techniques. Here's an example of a wrapper function that sanitizes user input before using it in a Sequelize query:

function sanitizeInput(input) {
  // Apply input validation and sanitization logic here
  return sanitizedInput;
}

const user = sanitizeInput(req.body.username);
const result = await User.findOne({ where: { username: user } });

Conclusion

The vulnerability in Sequelize versions prior to 3.0.0 exposes applications to the risk of SQL Injection. It is crucial to update to the latest version or apply proper input sanitization to prevent potential attacks. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for sequelize →

Share this vulnerability

FAQ

Sequelize is an Object-Relational Mapping (ORM) library for Node.js that simplifies database management by mapping database entries to objects.

SQL Injection is a type of security vulnerability that allows an attacker to manipulate SQL queries executed by an application, potentially bypassing authentication, accessing unauthorized data, or modifying the database.

If your application uses Sequelize versions prior to 3.0.0 and allows user input to be directly used in findOne or where statements, it is vulnerable to SQL Injection. An attacker can exploit this vulnerability to execute arbitrary SQL commands and potentially compromise the security of your application and its data.

To fix this vulnerability, update Sequelize to version 3.0.0 or later. If upgrading is not possible, ensure that all user input used in findOne or where statements is properly sanitized to prevent SQL Injection.

A temporary workaround is to sanitize user input before passing it to vulnerable functions. Implement a wrapper function that performs input validation and sanitization to mitigate the risk of SQL Injection.

Related vulnerabilities

Recent vulnerabilities recorded for sequelize.

How To Fix

Minimum fixed version

3.0.0

This is the first release that contains the fix.

npm install sequelize@3.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback