# CVE-2016-10550: Sequelize SQL injection in limit and order parameters

Source: https://junglewise.ai/threats/cve-2016-10550-sequelize-sql-injection-in-limit-and-order-parameters  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2019-02-18. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2016-10550 · Severity: info · CVSS 7.5 · Published 2019-02-18

Sequelize is a popular Node.js ORM (Object-Relational Mapping) library used to interact with databases. A SQL injection vulnerability exists in the limit and order query parameters, allowing attackers who control these inputs to inject arbitrary SQL code and potentially access, modify, or delete database records.

Technologies: [sequelize (npm)](https://junglewise.ai/threats/technologies/sequelize). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2016-10550 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2016-10550 being exploited in the wild.

**How severe is CVE-2016-10550?** Informational severity, with a CVSS score of 7.5, published 18 February 2019.

**Which products and versions are affected?** sequelize (npm) SEMVER:introduced=0,fixed=3.17.0.

**Is there a fix for CVE-2016-10550?** Yes. sequelize (npm): upgrade to 3.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2016-10550 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2016-10550?** Check whether you run sequelize (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- sequelize (npm): upgrade to 3.17.0 or later

  ```sh
  npm install sequelize@3.17.0
  ```


## Technical details

The vulnerability is a SQL injection (CWE-89) in the limit and order parameters of Sequelize query methods such as findOne() and findAll(). The root cause is insufficient escaping of user-supplied values passed to these parameters before incorporation into SQL statements. An attacker able to influence these parameters can inject malicious SQL fragments. The attack requires control over the limit or order parameter values in a query call. Patches were applied to escape these arguments, and the vulnerability is fixed in version 3.17.0 and later.

## Affected products

- Sequelize Sequelize before 3.17.0

## Identifiers

- CVE-2016-10550
- GHSA-98pq-pmw9-4gpm

## Timeline

- 2019-02-18: disclosed
- 2016-01-06: patched: Fix merged in Pull Request #5167

## References

- [https://github.com/sequelize/sequelize/pull/5167/commits/f282d85e60e3df5e57ecdb82adccb4eaef404f03](https://github.com/sequelize/sequelize/pull/5167/commits/f282d85e60e3df5e57ecdb82adccb4eaef404f03)

## Related threats

- [Sequelize SQL injection in Oracle dialect escape function](https://junglewise.ai/threats/cve-2026-69240-sequelize-sql-injection-in-oracle-dialect-escape-function)
- [Sequelize SQL injection in JSON where clause processing](https://junglewise.ai/threats/cve-2026-30951-sequelize-sql-injection-in-json-where-clause-processing)
- [Sequelize SQL injection via unescaped parentheses in attributes](https://junglewise.ai/threats/cve-2023-22578-sequelize-sql-injection-via-unescaped-parentheses-in-attributes)
- [Sequelize unsafe fall-through in getWhereConditions](https://junglewise.ai/threats/cve-2023-22579-sequelize-unsafe-fall-through-in-getwhereconditions)
- [Sequelize SQL injection via replacements](https://junglewise.ai/threats/cve-2023-25813-sequelize-sql-injection-via-replacements)