<?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>Tue, 13 Oct 2026 07:33:04 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-257309</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-257309</link>
      <description>EUVD-2026-257309</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-257309</guid>
    </item>
    <item>
      <title>fkie_cve-2025-60542</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-60542</link>
      <description>&lt;p&gt;SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-60542</guid>
    </item>
    <item>
      <title>GHSA-q2pj-6v73-8rgj — TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q2pj-6v73-8rgj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: typeorm&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Vulnerable Code:&lt;/p&gt;
&lt;p&gt;```js
const { username, city, name} = req.body;
const updateData = {
    username,
    city,
    name,
    id:userId
  }; // Developer aims to only allow above three fields to be updated    
const result = await userRepo.save(updateData);
```&lt;/p&gt;
&lt;p&gt;Intended Payload (non-malicious):&lt;/p&gt;
&lt;p&gt;`
username=myusername&amp;amp;city=Riga&amp;amp;name=Javad
`&lt;/p&gt;
&lt;p&gt;_OR_&lt;/p&gt;
&lt;p&gt;`{username:\&amp;#34;myusername\&amp;#34;,phone:12345,name:\&amp;#34;Javad\&amp;#34;}
`&lt;/p&gt;
&lt;p&gt;SQL query produced:&lt;/p&gt;
&lt;p&gt;```sql
UPDATE `user` 
SET `username` = &amp;#39;myusername&amp;#39;, 
    `city` = &amp;#39;Riga&amp;#39;, 
    `name` = &amp;#39;Javad&amp;#39; 
WHERE `id` IN (1);&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;Malicious Payload:&lt;/p&gt;
&lt;p&gt;`username=myusername&amp;amp;city[name]=Riga&amp;amp;city[role]=admin
`&lt;/p&gt;
&lt;p&gt;_OR_&lt;/p&gt;
&lt;p&gt;`{username:\&amp;#34;myusername\&amp;#34;,city:{name:\&amp;#34;Javad\&amp;#34;,role:\&amp;#34;admin\&amp;#34;}}
`&lt;/p&gt;
&lt;p&gt;SQL query produced with Injected Column:&lt;/p&gt;
&lt;p&gt;```sql
UPDATE `user` 
SET `username` = &amp;#39;myusername&amp;#39;, 
    `city` = `name` = &amp;#39;Javad&amp;#39;, 
    `role` = &amp;#39;admin&amp;#39; 
WHERE `id` IN (1);&lt;/p&gt;
&lt;p&gt;```
_Above query is valid as `city` = `name` = `Javad` is a boolean expression resulting in `city` = 1 (false). “role” column is injected and updated._&lt;/p&gt;
&lt;p&gt;Underlying issue was due to TypeORM using mysql2 [without specifying a value for the stringifyObjects option](https://github.com/typeorm/typeorm/blob/0.3.25/src/driver/mysql/MysqlConnectionOptions.ts). In both mysql and mysql2 this [option defaults to false](https://g…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: typeorm&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Vulnerable Code:&lt;/p&gt;
&lt;p&gt;```js
const { username, city, name} = req.body;
const updateData = {
    username,
    city,
    name,
    id:userId
  }; // Developer aims to only allow above three fields to be updated    
const result = await userRepo.save(updateData);
```&lt;/p&gt;
&lt;p&gt;Intended Payload (non-malicious):&lt;/p&gt;
&lt;p&gt;`
username=myusername&amp;amp;city=Riga&amp;amp;name=Javad
`&lt;/p&gt;
&lt;p&gt;_OR_&lt;/p&gt;
&lt;p&gt;`{username:\&amp;#34;myusername\&amp;#34;,phone:12345,name:\&amp;#34;Javad\&amp;#34;}
`&lt;/p&gt;
&lt;p&gt;SQL query produced:&lt;/p&gt;
&lt;p&gt;```sql
UPDATE `user` 
SET `username` = &amp;#39;myusername&amp;#39;, 
    `city` = &amp;#39;Riga&amp;#39;, 
    `name` = &amp;#39;Javad&amp;#39; 
WHERE `id` IN (1);&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;Malicious Payload:&lt;/p&gt;
&lt;p&gt;`username=myusername&amp;amp;city[name]=Riga&amp;amp;city[role]=admin
`&lt;/p&gt;
&lt;p&gt;_OR_&lt;/p&gt;
&lt;p&gt;`{username:\&amp;#34;myusername\&amp;#34;,city:{name:\&amp;#34;Javad\&amp;#34;,role:\&amp;#34;admin\&amp;#34;}}
`&lt;/p&gt;
&lt;p&gt;SQL query produced with Injected Column:&lt;/p&gt;
&lt;p&gt;```sql
UPDATE `user` 
SET `username` = &amp;#39;myusername&amp;#39;, 
    `city` = `name` = &amp;#39;Javad&amp;#39;, 
    `role` = &amp;#39;admin&amp;#39; 
WHERE `id` IN (1);&lt;/p&gt;
&lt;p&gt;```
_Above query is valid as `city` = `name` = `Javad` is a boolean expression resulting in `city` = 1 (false). “role” column is injected and updated._&lt;/p&gt;
&lt;p&gt;Underlying issue was due to TypeORM using mysql2 [without specifying a value for the stringifyObjects option](https://github.com/typeorm/typeorm/blob/0.3.25/src/driver/mysql/MysqlConnectionOptions.ts). In both mysql and mysql2 this [option defaults to false](https://g…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q2pj-6v73-8rgj</guid>
    </item>
    <item>
      <title>RHSA-2025:22404 — Red Hat Security Advisory: Red Hat Developer Hub 1.7.3 release.</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:22404</link>
      <description>&lt;p&gt;TypeORM: SQL Injection via crafted request to repository.save or repository.update&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;TypeORM: SQL Injection via crafted request to repository.save or repository.update&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:22404</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2702 — Red Hat Enterprise Linux (Developer Hub): Schwachstelle ermöglicht Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2702</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux Developer Hub ausnutzen, um eine SQL-Injection durchzuführen und möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu ändern oder Berechtigungen zu erweitern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux Developer Hub ausnutzen, um eine SQL-Injection durchzuführen und möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu ändern oder Berechtigungen zu erweitern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2702</guid>
    </item>
  </channel>
</rss>
