# CVE-2023-25813: SQL Injection via replacements in sequelize

> Attackers can execute arbitrary SQL commands via unescaped replacements in Sequelize queries, potentially reading or modifying database contents.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-wrh9-cjv3-2hpw

## What is CVE-2023-25813?

CVE-2023-25813 is a critical SQL injection vulnerability in sequelize, published on 22 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sequelize is a Node.js ORM tool. In versions prior to 6.19.1 a SQL injection exploit exists related to replacements. Parameters which are passed through replacements are not properly escaped which can lead to arbitrary SQL injection depending on the specific queries in use. The issue has been fixed in Sequelize 6.19.1. Users are advised to upgrade. Users unable to upgrade should not use the `replacements` and the `where` option in the same query.

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

## Which versions are affected by CVE-2023-25813?

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


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

Products: Sequelizejs Sequelize.

## How do I fix CVE-2023-25813?

Upgrade sequelize to 6.19.1 or later.

## Is CVE-2023-25813 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25813 exists.

Public exploit code:

- 12 (github_poc): https://github.com/White-BAO/CVE-2023-25813
- https://github.com/bde574786/Sequelize-1day-CVE-2023-25813 (github_poc): https://github.com/bde574786/Sequelize-1day-CVE-2023-25813
- https://github.com/pbj2647/CVE-2023-25813 (github_poc): https://github.com/pbj2647/CVE-2023-25813
- CVE-2023-25813 Vulnerability Reproduction - SQL Injection in Sequelize (github_poc): https://github.com/numbbvi/CVE-2023-25813
- https://github.com/sea-middle/cve-2023-25813 (github_poc): https://github.com/sea-middle/cve-2023-25813
- Sequelize Sql Injection 취약점 구현 (github_poc): https://github.com/h-gunp/CVE-2023-25813-TEST

## Other vulnerabilities in sequelize

- [CVE-2023-22578](https://insights.sbomify.com/CVE-2023-22578/): Sequalize - Default support for “raw attributes” when using parentheses (critical 10.0)
- [CVE-2023-22579](https://insights.sbomify.com/CVE-2023-22579/): Sequalize - Unsafe fall-through in getWhereConditions (critical 9.9)
- [CVE-2019-10749](https://insights.sbomify.com/CVE-2019-10749/): SQL Injection in sequelize (critical 9.8)
- [CVE-2019-10748](https://insights.sbomify.com/CVE-2019-10748/): SQL Injection in sequelize (critical 9.8)
- [CVE-2019-10752](https://insights.sbomify.com/CVE-2019-10752/): SQL Injection in sequelize (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25813 and fix it if it is affected.

What it is: CVE-2023-25813 is a critical SQL injection vulnerability in sequelize, published on 22 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25813 exists.

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

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-2023-25813/ (Markdown: https://insights.sbomify.com/CVE-2023-25813/index.md)
```

## Sources

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

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