<?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 09:08:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-343333</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343333</link>
      <description>EUVD-2026-343333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343333</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63222</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63222</link>
      <description>&lt;p&gt;CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, calling UploadedFile::move() without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory when the application exposes an upload path. This issue is fixed in version 4.7.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, calling UploadedFile::move() without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory when the application exposes an upload path. This issue is fixed in version 4.7.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-63222</guid>
    </item>
    <item>
      <title>GHSA-hhmc-q9hp-r662 — CodeIgniter: Path traversal in UploadedFile::move() when using client-provided filenames</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hhmc-q9hp-r662</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: codeigniter4/framework&lt;/p&gt;
&lt;p&gt;### Impact
In affected versions, calling `UploadedFile::move()` **without a second argument** uses the client-provided filename without sanitization. Depending on the destination path and server configuration, an attacker can supply a filename containing path traversal sequences (e.g. `../../public/shell.php`) to write uploaded content outside the intended upload directory.&lt;/p&gt;
&lt;p&gt;The patch sanitizes this default (no-argument) path.&lt;/p&gt;
&lt;p&gt;**Note:** The patch only sanitizes the filename when no second argument is passed. If your application **explicitly** passes a client-provided name as the second argument, you remain responsible for sanitizing it - the patch does not (and cannot) sanitize a caller-supplied filename:
```php
// Unsafe - even after upgrading:
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $file-&amp;gt;getName());
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $file-&amp;gt;getClientName());
```&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to v4.7.4 or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
If you cannot upgrade immediately, use a generated filename or sanitize the client filename before passing it to `move()`.&lt;/p&gt;
&lt;p&gt;Use a generated filename:
```php
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $file-&amp;gt;getRandomName());
```
Or sanitize the client filename before passing it to `move()`:
```php
helper(&amp;#39;security&amp;#39;);&lt;/p&gt;
&lt;p&gt;$name = sanitize_filename($file-&amp;gt;getClientName());
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $name);
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: codeigniter4/framework&lt;/p&gt;
&lt;p&gt;### Impact
In affected versions, calling `UploadedFile::move()` **without a second argument** uses the client-provided filename without sanitization. Depending on the destination path and server configuration, an attacker can supply a filename containing path traversal sequences (e.g. `../../public/shell.php`) to write uploaded content outside the intended upload directory.&lt;/p&gt;
&lt;p&gt;The patch sanitizes this default (no-argument) path.&lt;/p&gt;
&lt;p&gt;**Note:** The patch only sanitizes the filename when no second argument is passed. If your application **explicitly** passes a client-provided name as the second argument, you remain responsible for sanitizing it - the patch does not (and cannot) sanitize a caller-supplied filename:
```php
// Unsafe - even after upgrading:
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $file-&amp;gt;getName());
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $file-&amp;gt;getClientName());
```&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to v4.7.4 or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
If you cannot upgrade immediately, use a generated filename or sanitize the client filename before passing it to `move()`.&lt;/p&gt;
&lt;p&gt;Use a generated filename:
```php
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $file-&amp;gt;getRandomName());
```
Or sanitize the client filename before passing it to `move()`:
```php
helper(&amp;#39;security&amp;#39;);&lt;/p&gt;
&lt;p&gt;$name = sanitize_filename($file-&amp;gt;getClientName());
$file-&amp;gt;move(WRITEPATH . &amp;#39;uploads&amp;#39;, $name);
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hhmc-q9hp-r662</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63222</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63222</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: php-codeigniter-framework, Ubuntu:26.04:LTS: php-codeigniter-framework&lt;/p&gt;
&lt;p&gt;CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, calling UploadedFile::move() without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory when the application exposes an upload path. This issue is fixed in version 4.7.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: php-codeigniter-framework, Ubuntu:26.04:LTS: php-codeigniter-framework&lt;/p&gt;
&lt;p&gt;CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, calling UploadedFile::move() without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory when the application exposes an upload path. This issue is fixed in version 4.7.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63222</guid>
    </item>
  </channel>
</rss>
