# CVE-2015-1369: SQL Injection in sequelize

> Remote attackers can execute arbitrary SQL commands via the order parameter in Sequelize, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xqg8-cv3h-xppv

## What is CVE-2015-1369?

CVE-2015-1369 is a high-severity SQL injection vulnerability in n/a, published on 27 Jan 2015. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in Sequelize before 2.0.0-rc7 for Node.js allows remote attackers to execute arbitrary SQL commands via the order parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2015-1369?

2 open source packages ship an affected version, including sequelize. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sequelize` | npm | All versions | 2.0.0-rc8 |
| `sequelize` | npm | All versions | 2.0.0-rc8 |

Products: Sequelize Project Sequelize.

## How do I fix CVE-2015-1369?

Upgrade sequelize to 2.0.0-rc8 or later.

## Is CVE-2015-1369 being exploited?

There is no known exploitation of CVE-2015-1369 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1369 and fix it if it is affected.

What it is: CVE-2015-1369 is a high-severity SQL injection vulnerability in n/a, published on 27 Jan 2015. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1369 in the wild and no public exploit code.

Affected packages and fixed versions:
- sequelize (npm): affected all versions; fixed in 2.0.0-rc8
- sequelize (npm): affected all versions; fixed in 2.0.0-rc8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-1369/ (Markdown: https://insights.sbomify.com/CVE-2015-1369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-1369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-1369
- OSV: https://osv.dev/vulnerability/CVE-2015-1369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-1369/
Summaries are generated and may contain mistakes; the official description above is the record.