{"id":"GHSA-wrh9-cjv3-2hpw","revision":"c2cfa11c38fd4fae95ea8fe7ba0675ff","records":[{"revision":"c2cfa11c38fd4fae95ea8fe7ba0675ff","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-wrh9-cjv3-2hpw","aliases":["CVE-2023-25813"],"title":"Sequelize vulnerable to SQL Injection via replacements","description":"### Impact\n\nThe SQL injection exploit is related to replacements. Here is such an example: \n\nIn the following query, some parameters are passed through replacements, and some are passed directly through the `where` option.\n\n```typescript\nUser.findAll({\n  where: or(\n    literal('soundex(\"firstName\") = soundex(:firstName)'),\n    { lastName: lastName },\n  ),\n  replacements: { firstName },\n})\n```\n\nThis is a very legitimate use case, but this query was vulnerable to SQL injection due to how Sequelize processed the query: Sequelize built a first query using the `where` option, then passed it over to `sequelize.query` which parsed the resulting SQL to inject all `:replacements`.\n\nIf the user passed values such as\n\n```json\n{\n  \"firstName\": \"OR true; DROP TABLE users;\",\n  \"lastName\": \":firstName\"\n}\n```\n\nSequelize would first generate this query:\n\n```sql\nSELECT * FROM users WHERE soundex(\"firstName\") = soundex(:firstName) OR \"lastName\" = ':firstName'\n```\n\nThen would inject replacements in it, which resulted in this:\n\n```sql\nSELECT * FROM users WHERE soundex(\"firstName\") = soundex('OR true; DROP TABLE users;') OR \"lastName\" = ''OR true; DROP TABLE users;''\n```\n\nAs you can see this resulted in arbitrary user-provided SQL being executed.\n\n### Patches\n\nThe issue was fixed in Sequelize 6.19.1\n\n### Workarounds\n\nDo not use the `replacements` and the `where` option in the same query if you are not using Sequelize >= 6.19.1 \n\n### References\n\nSee this thread for more information: https://github.com/sequelize/sequelize/issues/14519\n\nSnyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-2932027","state":0,"publishedAt":"2023-02-22T22:59:09+00:00","modifiedAt":"2026-09-10T03:49:52.0985799+00:00","affected":[{"ecosystem":"npm","name":"sequelize","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"6.19.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"CRITICAL"}],"references":["https://github.com/sequelize/sequelize/security/advisories/GHSA-wrh9-cjv3-2hpw","https://nvd.nist.gov/vuln/detail/CVE-2023-25813","https://github.com/sequelize/sequelize/issues/14519","https://github.com/sequelize/sequelize/commit/ccaa3996047fe00048d5993ab2dd43ebadd4f78b","https://github.com/sequelize/sequelize","https://github.com/sequelize/sequelize/releases/tag/v6.19.1","https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-2932027"],"sourceUrl":"https://github.com/advisories/GHSA-wrh9-cjv3-2hpw","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-wrh9-cjv3-2hpw","identifiers":["GHSA-wrh9-cjv3-2hpw","CVE-2023-25813"]},"retained":false,"historicalAffected":[]}],"coverage":[]}