<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 02:45:38 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-221524</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-221524</link>
      <description>EUVD-2026-221524</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-221524</guid>
    </item>
    <item>
      <title>fkie_cve-2023-25813</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-25813</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-25813</guid>
    </item>
    <item>
      <title>GHSA-wrh9-cjv3-2hpw — Sequelize vulnerable to SQL Injection via replacements</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wrh9-cjv3-2hpw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sequelize&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The SQL injection exploit is related to replacements. Here is such an example:&lt;/p&gt;
&lt;p&gt;In the following query, some parameters are passed through replacements, and some are passed directly through the `where` option.&lt;/p&gt;
&lt;p&gt;```typescript
User.findAll({
  where: or(
    literal(&amp;#39;soundex(&amp;#34;firstName&amp;#34;) = soundex(:firstName)&amp;#39;),
    { lastName: lastName },
  ),
  replacements: { firstName },
})
```&lt;/p&gt;
&lt;p&gt;This 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`.&lt;/p&gt;
&lt;p&gt;If the user passed values such as&lt;/p&gt;
&lt;p&gt;```json
{
  &amp;#34;firstName&amp;#34;: &amp;#34;OR true; DROP TABLE users;&amp;#34;,
  &amp;#34;lastName&amp;#34;: &amp;#34;:firstName&amp;#34;
}
```&lt;/p&gt;
&lt;p&gt;Sequelize would first generate this query:&lt;/p&gt;
&lt;p&gt;```sql
SELECT * FROM users WHERE soundex(&amp;#34;firstName&amp;#34;) = soundex(:firstName) OR &amp;#34;lastName&amp;#34; = &amp;#39;:firstName&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Then would inject replacements in it, which resulted in this:&lt;/p&gt;
&lt;p&gt;```sql
SELECT * FROM users WHERE soundex(&amp;#34;firstName&amp;#34;) = soundex(&amp;#39;OR true; DROP TABLE users;&amp;#39;) OR &amp;#34;lastName&amp;#34; = &amp;#39;&amp;#39;OR true; DROP TABLE users;&amp;#39;&amp;#39;
```&lt;/p&gt;
&lt;p&gt;As you can see this resulted in arbitrary user-provided SQL being executed.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue was fixed in Sequelize 6.19.1&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Do not use the `replacements` and the `where` option in the same query if you are not using Sequelize &amp;gt;= 6.19.1&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;See this thread for more information: https://github…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sequelize&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The SQL injection exploit is related to replacements. Here is such an example:&lt;/p&gt;
&lt;p&gt;In the following query, some parameters are passed through replacements, and some are passed directly through the `where` option.&lt;/p&gt;
&lt;p&gt;```typescript
User.findAll({
  where: or(
    literal(&amp;#39;soundex(&amp;#34;firstName&amp;#34;) = soundex(:firstName)&amp;#39;),
    { lastName: lastName },
  ),
  replacements: { firstName },
})
```&lt;/p&gt;
&lt;p&gt;This 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`.&lt;/p&gt;
&lt;p&gt;If the user passed values such as&lt;/p&gt;
&lt;p&gt;```json
{
  &amp;#34;firstName&amp;#34;: &amp;#34;OR true; DROP TABLE users;&amp;#34;,
  &amp;#34;lastName&amp;#34;: &amp;#34;:firstName&amp;#34;
}
```&lt;/p&gt;
&lt;p&gt;Sequelize would first generate this query:&lt;/p&gt;
&lt;p&gt;```sql
SELECT * FROM users WHERE soundex(&amp;#34;firstName&amp;#34;) = soundex(:firstName) OR &amp;#34;lastName&amp;#34; = &amp;#39;:firstName&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Then would inject replacements in it, which resulted in this:&lt;/p&gt;
&lt;p&gt;```sql
SELECT * FROM users WHERE soundex(&amp;#34;firstName&amp;#34;) = soundex(&amp;#39;OR true; DROP TABLE users;&amp;#39;) OR &amp;#34;lastName&amp;#34; = &amp;#39;&amp;#39;OR true; DROP TABLE users;&amp;#39;&amp;#39;
```&lt;/p&gt;
&lt;p&gt;As you can see this resulted in arbitrary user-provided SQL being executed.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue was fixed in Sequelize 6.19.1&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Do not use the `replacements` and the `where` option in the same query if you are not using Sequelize &amp;gt;= 6.19.1&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;See this thread for more information: https://github…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wrh9-cjv3-2hpw</guid>
    </item>
    <item>
      <title>gsd-2023-25813</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-25813</link>
      <description>gsd-2023-25813</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-25813</guid>
    </item>
  </channel>
</rss>
