<?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:11:22 +0000</lastBuildDate>
    <item>
      <title>cnvd-2018-10673</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-10673</link>
      <description>cnvd-2018-10673</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-10673</guid>
    </item>
    <item>
      <title>EUVD-2026-184517</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-184517</link>
      <description>EUVD-2026-184517</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-184517</guid>
    </item>
    <item>
      <title>fkie_cve-2016-10556</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2016-10556</link>
      <description>&lt;p&gt;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 `[&amp;#34;test&amp;#34;, &amp;#34;&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)&amp;#34;]` inside of ``` database.query(&amp;#39;SELECT * FROM TestTable WHERE Name IN (:names)&amp;#39;, { replacements: { names: directCopyOfUserInput } }); ``` and cause the SQL statement to become `SELECT Id FROM Table WHERE Name IN (&amp;#39;test&amp;#39;, &amp;#39;\&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)`. 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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 `[&amp;#34;test&amp;#34;, &amp;#34;&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)&amp;#34;]` inside of ``` database.query(&amp;#39;SELECT * FROM TestTable WHERE Name IN (:names)&amp;#39;, { replacements: { names: directCopyOfUserInput } }); ``` and cause the SQL statement to become `SELECT Id FROM Table WHERE Name IN (&amp;#39;test&amp;#39;, &amp;#39;\&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)`. 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2016-10556</guid>
    </item>
    <item>
      <title>GHSA-9c2p-jw8p-f84v — SQL Injection in sequelize</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9c2p-jw8p-f84v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sequelize&lt;/p&gt;
&lt;p&gt;Affected versions of `sequelize` cast arrays to strings and fail to properly escape the resulting SQL statement, resulting in a SQL injection vulnerability.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
In Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped.&lt;/p&gt;
&lt;p&gt;Example Query:
```
database.query(&amp;#39;SELECT * FROM TestTable WHERE Name IN (:names)&amp;#39;, {
  replacements: {
    names: directCopyOfUserInput
  }
});
```&lt;/p&gt;
&lt;p&gt;If the user inputs the value of `:names` as:
```
[&amp;#34;test&amp;#34;, &amp;#34;&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)&amp;#34;]
```&lt;/p&gt;
&lt;p&gt;The resulting SQL statement will be:
```sql
SELECT Id FROM Table WHERE Name IN (&amp;#39;test&amp;#39;, &amp;#39;\&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)
```
As the backslash has no special meaning in PostgreSQL, MSSQL, or SQLite, the statement will delete the record in TestTable with an Id of 1.&lt;/p&gt;
&lt;p&gt;## Recommendation&lt;/p&gt;
&lt;p&gt;Update to version 3.20.0 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sequelize&lt;/p&gt;
&lt;p&gt;Affected versions of `sequelize` cast arrays to strings and fail to properly escape the resulting SQL statement, resulting in a SQL injection vulnerability.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
In Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped.&lt;/p&gt;
&lt;p&gt;Example Query:
```
database.query(&amp;#39;SELECT * FROM TestTable WHERE Name IN (:names)&amp;#39;, {
  replacements: {
    names: directCopyOfUserInput
  }
});
```&lt;/p&gt;
&lt;p&gt;If the user inputs the value of `:names` as:
```
[&amp;#34;test&amp;#34;, &amp;#34;&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)&amp;#34;]
```&lt;/p&gt;
&lt;p&gt;The resulting SQL statement will be:
```sql
SELECT Id FROM Table WHERE Name IN (&amp;#39;test&amp;#39;, &amp;#39;\&amp;#39;); DELETE TestTable WHERE Id = 1 --&amp;#39;)
```
As the backslash has no special meaning in PostgreSQL, MSSQL, or SQLite, the statement will delete the record in TestTable with an Id of 1.&lt;/p&gt;
&lt;p&gt;## Recommendation&lt;/p&gt;
&lt;p&gt;Update to version 3.20.0 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9c2p-jw8p-f84v</guid>
    </item>
    <item>
      <title>gsd-2016-10556</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2016-10556</link>
      <description>gsd-2016-10556</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2016-10556</guid>
    </item>
  </channel>
</rss>
