CVE-2019-11069 json
SQL Injection in sequelize
published 2019-04-10 7 y ago modified 2026-06-17 4 mo ago also GHSA-2777-2vq8-c4v4 , EUVD-2019-0399
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Sequelize version 5 before 5.3.0 does not properly ensure that standard conforming strings are used.
Patch / fix
- npm sequelize 5.3.0
- sequelizejs sequelize 5.3.0
- github.com/sequelize/sequelize@850c7fd commit
- github.com/sequelize/sequelize#10746 pull request
- github.com/sequelize/sequelize#10746 pull request
- github.com/sequelize/sequelize/releases/tag/v5.3.0 release
Exploit prediction
1.82% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | sequelize | >=5.0.0, <5.3.0 |
5.3.0 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/sequelize/sequelize/pull/10746/files
web, patch, third-party-advisory
-
github.com
/sequelize/sequelize/commit/850c7fd04669e0fef9238b6dc4f8d6ee93ed71e9
web
-
github.com
/sequelize/sequelize/pull/10746
web
-
github.com
/sequelize/sequelize/releases/tag/v5.3.0
web, release-notes, third-party-advisory
-
github.com
/sequelize/sequelize/blob/98cb17c17f73e2aa1792aa5a1d31216ba984b456/lib/dialects/postgres/connection-manager.js
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-11069
advisory
-
github.com
/sequelize/sequelize
package
-
snyk.io
/vuln/SNYK-JS-SEQUELIZE-174167
web
Sources
- CVE List CVE-2019-11069
- GitHub Advisory GHSA-2777-2vq8-c4v4
- NVD CVE-2019-11069
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.