CVE-2019-10748: SQL Injection in sequelize

sequelize Updated 02 Oct 2025

Summary

06/11/2019
Yes i
Critical
9.8

CVE-2019-10748: SQL Injection in sequelize. Affects sequelize across 3 version ranges.

< 3.35.1 >= 4.0.0, < 4.44.3 >= 5.0.0, < 5.8.11

Fixed in 3.35.1, 4.44.3 or 5.8.11, depending on the release line you run. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Sequelize is an Object-Relational Mapping (ORM) library for Node.js that provides easy access to databases by mapping database entries to JavaScript objects. It is widely used for building web applications and APIs. However, versions of sequelize prior to 5.8.11 (for 5.x), 4.44.3 (for 4.x), and 3.35.1 (for 3.x) are vulnerable to SQL Injection.

Vulnerability Detail

The vulnerability in sequelize arises from the package's failure to properly sanitize JSON path keys in the MariaDB and MySQL dialects. This allows attackers to inject malicious SQL statements and execute arbitrary SQL queries. An attacker can exploit this vulnerability to gain unauthorized access to the database, modify data, or perform other malicious actions.

How To Fix

Latest published version: 6.37.8 as of 23 Oct 2026

npm install sequelize@6.37.8

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 3.35.1 3.35.1
    npm install sequelize@3.35.1
  • >= 4.0.0, < 4.44.3 4.44.3
    npm install sequelize@4.44.3
  • >= 5.0.0, < 5.8.11 5.8.11
    npm install sequelize@5.8.11

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. Upgrading to the fixed versions is the recommended solution.

Conclusion

In conclusion, the sequelize package versions prior to the fixed versions mentioned are vulnerable to SQL Injection. It is crucial to upgrade to the recommended versions to mitigate the risk of unauthorized database access and potential data manipulation. 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 access and manipulation by mapping database entries to JavaScript objects.

SQL Injection is a type of security vulnerability where an attacker can insert malicious SQL statements into an application's database query. This can lead to unauthorized access, data manipulation, or other malicious actions.

An attacker can exploit this vulnerability by crafting malicious JSON path keys in the MariaDB or MySQL dialects, which are not properly sanitized by sequelize. This allows the attacker to inject SQL statements and execute arbitrary SQL queries.

The consequences of this vulnerability include unauthorized access to the database, data manipulation, data theft, and potential compromise of the entire application or system.

The only known mitigation is to upgrade to the fixed versions of sequelize as recommended.

Related vulnerabilities

Recent vulnerabilities recorded for sequelize.

How To Fix

Latest published version: 6.37.8 as of 23 Oct 2026

npm install sequelize@6.37.8

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 3.35.1 3.35.1
    npm install sequelize@3.35.1
  • >= 4.0.0, < 4.44.3 4.44.3
    npm install sequelize@4.44.3
  • >= 5.0.0, < 5.8.11 5.8.11
    npm install sequelize@5.8.11

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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