ZeroHour

Vulnerabilities

14 CVEs · NVD, GitHub Advisories, CISA KEV, FIRST EPSS, GitHub PoC repos

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-30951
Sequelize is a Node.js ORM tool.

Sequelize is a Node.js ORM tool. Prior to 6.37.8, there is SQL injection via unescaped cast type in JSON/JSONB where clause processing. The _traverseJSON() function splits JSON path keys on :: to extract a cast type, which is interpolated raw into CAST(... AS ) SQL. An attacker who controls JSON object keys can inject arbitrary SQL and exfiltrate data from any table. This vulnerability is fixed in 6.37.8.

NVD description · AI analysis pending
7.5<1% PoC
  • sequelizejs sequelize
CVE-2023-6293
Prototype Pollution in GitHub repository robinbuschmann/sequelize-typescript prior to 2.1.6.

Prototype Pollution in GitHub repository robinbuschmann/sequelize-typescript prior to 2.1.6.

NVD description · AI analysis pending
7.1<1% PoC
  • sequelizejs sequelize-typescript
CVE-2023-25813
Sequelize is a Node.js ORM tool.

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.

NVD description · AI analysis pending
9.81% PoC ×2
  • sequelizejs sequelize
CVE-2023-22578
+2 in the same advisory: …22579 …22580
Due to improper artibute filtering in the sequalize js library, can a attacker peform SQL injections.

Due to improper artibute filtering in the sequalize js library, can a attacker peform SQL injections.

NVD description · AI analysis pending
9.8
group max
<1%
  • sequelizejs sequelize
CVE-2019-10748
+1 in the same advisory: …10749
Sequelize all versions prior to 3.35.1, 4.44.3, and 5.8.11 are vulnerable to SQL Injection due to JSON path keys not being properly escaped for the MySQL/MariaD

Sequelize all versions prior to 3.35.1, 4.44.3, and 5.8.11 are vulnerable to SQL Injection due to JSON path keys not being properly escaped for the MySQL/MariaDB dialects.

NVD description · AI analysis pending
9.81% PoC
  • sequelizejs sequelize
CVE-2019-10752
Sequelize, all versions prior to version 4.44.3 and 5.15.1, is vulnerable to SQL Injection due to sequelize.json() helper function not escaping values properly

Sequelize, all versions prior to version 4.44.3 and 5.15.1, is vulnerable to SQL Injection due to sequelize.json() helper function not escaping values properly when formatting sub paths for JSON queries for MySQL, MariaDB and SQLite.

NVD description · AI analysis pending
9.81% PoC
  • sequelizejs sequelize
CVE-2019-11069
Sequelize version 5 before 5.3.0 does not properly ensure that standard conforming strings are used.

Sequelize version 5 before 5.3.0 does not properly ensure that standard conforming strings are used.

NVD description · AI analysis pending
7.52%
  • sequelizejs sequelize
CVE-2016-10554
+2 in the same advisory: …10550 …10553
sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for

sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS. Before version 1.7.0-alpha3, sequelize defaulted SQLite to use MySQL backslash escaping, even though SQLite uses Postgres escaping.

NVD description · AI analysis pending
9.82%
  • sequelizejs sequelize
CVE-2016-10556
sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for

sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS In Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped. This causes potential SQL injection in sequelize 3.19.3 and earlier, where a malicious user could put `["test", "'); DELETE TestTable WHERE Id = 1 --')"]` inside of ``` database.query('SELECT * FROM TestTable WHERE Name IN (:names)', { replacements: { names: directCopyOfUserInput } }); ``` and cause the SQL statement to become `SELECT Id FROM Table WHERE Name IN ('test', '\'); DELETE TestTable WHERE Id = 1 --')`. In Postgres, MSSQL, and SQLite, the backslash has no special meaning. This causes the the statement to delete whichever Id has a value of 1 in the TestTable table.

NVD description · AI analysis pending
7.51% PoC
  • sequelizejs sequelize