<?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 18:13:42 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-343532</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343532</link>
      <description>EUVD-2026-343532</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343532</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63223</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63223</link>
      <description>&lt;p&gt;CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. 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, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. 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-63223</guid>
    </item>
    <item>
      <title>GHSA-mmj4-63m4-r6h5 — CodeIgniter: Uploaded file extension validation bypass in `is_image` and `mime_in` rules</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mmj4-63m4-r6h5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: codeigniter4/framework&lt;/p&gt;
&lt;p&gt;### Impact
This is an unsafe file upload validation vulnerability that can lead to remote code execution in vulnerable application configurations.&lt;/p&gt;
&lt;p&gt;Applications are impacted when they:
- validate uploads using `is_image` or `mime_in` without an independent safe extension check, such as `ext_in` on patched versions
- save uploaded files using the client-supplied filename
- place uploads in a web-accessible directory where PHP files can execute&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to v4.7.4 or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
- Save uploads outside the public web root, preferably under `writable/uploads`.
- Use `$file-&amp;gt;store()` or `$file-&amp;gt;move($path, $file-&amp;gt;getRandomName())` instead of preserving the original client filename.
- Disable script execution in any public upload directory.
- Manually verify the client filename extension before moving the file.
- For image uploads, reject files when `$file-&amp;gt;getClientExtension()` is not an allowed image extension.
- For exact MIME-type validation, reject files when `$file-&amp;gt;getClientExtension()` does not match `$file-&amp;gt;guessExtension()`.&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
This is an unsafe file upload validation vulnerability that can lead to remote code execution in vulnerable application configurations.&lt;/p&gt;
&lt;p&gt;Applications are impacted when they:
- validate uploads using `is_image` or `mime_in` without an independent safe extension check, such as `ext_in` on patched versions
- save uploaded files using the client-supplied filename
- place uploads in a web-accessible directory where PHP files can execute&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to v4.7.4 or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
- Save uploads outside the public web root, preferably under `writable/uploads`.
- Use `$file-&amp;gt;store()` or `$file-&amp;gt;move($path, $file-&amp;gt;getRandomName())` instead of preserving the original client filename.
- Disable script execution in any public upload directory.
- Manually verify the client filename extension before moving the file.
- For image uploads, reject files when `$file-&amp;gt;getClientExtension()` is not an allowed image extension.
- For exact MIME-type validation, reject files when `$file-&amp;gt;getClientExtension()` does not match `$file-&amp;gt;guessExtension()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mmj4-63m4-r6h5</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63223</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63223</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, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. 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, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. 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-63223</guid>
    </item>
  </channel>
</rss>
