<?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, 06 Oct 2026 10:03:45 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-318539</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-318539</link>
      <description>EUVD-2026-318539</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-318539</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42550</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42550</link>
      <description>&lt;p&gt;Flight is an extensible micro-framework for PHP. Prior to 3.18.1, SimplePdo::insert(), SimplePdo::update(), and SimplePdo::delete() build SQL statements by concatenating the $table argument and the keys of the $data array directly into the query, with no identifier quoting and no validation. When an application forwards user-controlled data shapes to these helpers — a common and documented pattern, e.g. $db-&amp;gt;insert(&amp;#39;users&amp;#39;, $request-&amp;gt;data-&amp;gt;getData()) — an attacker can inject arbitrary SQL by crafting malicious array keys. This vulnerability is fixed in 3.18.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flight is an extensible micro-framework for PHP. Prior to 3.18.1, SimplePdo::insert(), SimplePdo::update(), and SimplePdo::delete() build SQL statements by concatenating the $table argument and the keys of the $data array directly into the query, with no identifier quoting and no validation. When an application forwards user-controlled data shapes to these helpers — a common and documented pattern, e.g. $db-&amp;gt;insert(&amp;#39;users&amp;#39;, $request-&amp;gt;data-&amp;gt;getData()) — an attacker can inject arbitrary SQL by crafting malicious array keys. This vulnerability is fixed in 3.18.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42550</guid>
    </item>
    <item>
      <title>GHSA-xwqr-rcqg-22mr — Flight vulnerable to SQL Injection via unvalidated identifiers in SimplePdo::insert / update / delete</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xwqr-rcqg-22mr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flightphp/core&lt;/p&gt;
&lt;p&gt;### Summary
`SimplePdo::insert()`, `SimplePdo::update()`, and `SimplePdo::delete()` build SQL statements by concatenating the `$table` argument and the **keys** of the `$data` array directly into the query, with no identifier quoting and no validation. When an application forwards user-controlled data shapes to these helpers — a common and documented pattern, e.g. `$db-&amp;gt;insert(&amp;#39;users&amp;#39;, $request-&amp;gt;data-&amp;gt;getData())` — an attacker can inject arbitrary SQL by crafting malicious array keys.&lt;/p&gt;
&lt;p&gt;### Affected code
`flight/database/SimplePdo.php`:&lt;/p&gt;
&lt;p&gt;```php
// insert (≈ 320-373)
$sql = sprintf(
    &amp;#34;INSERT INTO %s (%s) VALUES (%s)&amp;#34;,
    $table,                            // raw concat
    implode(&amp;#39;, &amp;#39;, $columns),           // raw array_keys($data)
    implode(&amp;#39;, &amp;#39;, $placeholders)
);&lt;/p&gt;
&lt;p&gt;// update (≈ 397-409)
$sets[] = &amp;#34;$column = ?&amp;#34;;               // $column = user-controlled key
$sql = sprintf(
    &amp;#34;UPDATE %s SET %s WHERE %s&amp;#34;,
    $table,                            // raw
    implode(&amp;#39;, &amp;#39;, $sets),
    $where
);&lt;/p&gt;
&lt;p&gt;// delete (≈ 427-429)
$sql = &amp;#34;DELETE FROM $table WHERE $where&amp;#34;;
```&lt;/p&gt;
&lt;p&gt;No identifier-quoting helper exists; neither `$table` nor the data keys are validated against a safe-identifier pattern.&lt;/p&gt;
&lt;p&gt;### Proof of concept
A controller does:
```php
$db-&amp;gt;insert(&amp;#39;users&amp;#39;, $request-&amp;gt;data-&amp;gt;getData());
```&lt;/p&gt;
&lt;p&gt;The attacker sends the JSON body:
```json
{&amp;#34;name, is_admin) VALUES (?, 1);-- &amp;#34;: &amp;#34;attacker_injected&amp;#34;}
```&lt;/p&gt;
&lt;p&gt;Generated SQL:
```sql
INSERT INTO users (name, is_admin) VALUES (?, 1);-- ) VALUES (?)
```…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flightphp/core&lt;/p&gt;
&lt;p&gt;### Summary
`SimplePdo::insert()`, `SimplePdo::update()`, and `SimplePdo::delete()` build SQL statements by concatenating the `$table` argument and the **keys** of the `$data` array directly into the query, with no identifier quoting and no validation. When an application forwards user-controlled data shapes to these helpers — a common and documented pattern, e.g. `$db-&amp;gt;insert(&amp;#39;users&amp;#39;, $request-&amp;gt;data-&amp;gt;getData())` — an attacker can inject arbitrary SQL by crafting malicious array keys.&lt;/p&gt;
&lt;p&gt;### Affected code
`flight/database/SimplePdo.php`:&lt;/p&gt;
&lt;p&gt;```php
// insert (≈ 320-373)
$sql = sprintf(
    &amp;#34;INSERT INTO %s (%s) VALUES (%s)&amp;#34;,
    $table,                            // raw concat
    implode(&amp;#39;, &amp;#39;, $columns),           // raw array_keys($data)
    implode(&amp;#39;, &amp;#39;, $placeholders)
);&lt;/p&gt;
&lt;p&gt;// update (≈ 397-409)
$sets[] = &amp;#34;$column = ?&amp;#34;;               // $column = user-controlled key
$sql = sprintf(
    &amp;#34;UPDATE %s SET %s WHERE %s&amp;#34;,
    $table,                            // raw
    implode(&amp;#39;, &amp;#39;, $sets),
    $where
);&lt;/p&gt;
&lt;p&gt;// delete (≈ 427-429)
$sql = &amp;#34;DELETE FROM $table WHERE $where&amp;#34;;
```&lt;/p&gt;
&lt;p&gt;No identifier-quoting helper exists; neither `$table` nor the data keys are validated against a safe-identifier pattern.&lt;/p&gt;
&lt;p&gt;### Proof of concept
A controller does:
```php
$db-&amp;gt;insert(&amp;#39;users&amp;#39;, $request-&amp;gt;data-&amp;gt;getData());
```&lt;/p&gt;
&lt;p&gt;The attacker sends the JSON body:
```json
{&amp;#34;name, is_admin) VALUES (?, 1);-- &amp;#34;: &amp;#34;attacker_injected&amp;#34;}
```&lt;/p&gt;
&lt;p&gt;Generated SQL:
```sql
INSERT INTO users (name, is_admin) VALUES (?, 1);-- ) VALUES (?)
```…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xwqr-rcqg-22mr</guid>
    </item>
  </channel>
</rss>
