<?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>Mon, 12 Oct 2026 23:11:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-308984</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-308984</link>
      <description>EUVD-2026-308984</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-308984</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41890</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41890</link>
      <description>&lt;p&gt;CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. From version 0.31.1.0 to before version 0.31.8.0, the deleteProcess() action accepts a POST parameter tables[] containing arbitrary table names. These are passed directly to $forge-&amp;gt;dropTable() without validating that the tables belong to the theme being deleted. The deleteConfirm view correctly populates tables[] from the theme&amp;#39;s own migration files, but the server-side deleteProcess does not verify the received values against those files. An authenticated admin can craft a POST request with arbitrary table names and drop any table in the database. This issue has been patched in version 0.31.8.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. From version 0.31.1.0 to before version 0.31.8.0, the deleteProcess() action accepts a POST parameter tables[] containing arbitrary table names. These are passed directly to $forge-&amp;gt;dropTable() without validating that the tables belong to the theme being deleted. The deleteConfirm view correctly populates tables[] from the theme&amp;#39;s own migration files, but the server-side deleteProcess does not verify the received values against those files. An authenticated admin can craft a POST request with arbitrary table names and drop any table in the database. This issue has been patched in version 0.31.8.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41890</guid>
    </item>
    <item>
      <title>GHSA-vgrf-pr28-vf98 — CI4MS Vulnerable to Arbitrary Database Table Drop via Theme deleteProcess</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vgrf-pr28-vf98</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ci4-cms-erp/ci4ms&lt;/p&gt;
&lt;p&gt;### Summary
The `deleteProcess()` action accepts a POST parameter `tables[]` containing arbitrary table names. These are passed directly to `$forge-&amp;gt;dropTable()` without validating that the tables belong to the theme being deleted.&lt;/p&gt;
&lt;p&gt;The `deleteConfirm` view correctly populates `tables[]` from the theme&amp;#39;s own migration files, but the server-side `deleteProcess` does not verify the received values against those files. An authenticated admin can craft a POST request with arbitrary table names and drop any table in the database.&lt;/p&gt;
&lt;p&gt;This is a real bug even within the admin trust model: the action should be scoped to the theme&amp;#39;s own tables. The permission grants  delete this theme&amp;#39;s data&amp;#34;, not &amp;#34;drop any table&amp;#34;.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;### Location
`modules/Theme/Controllers/Theme.php` :: `deleteProcess()` ~line 147&lt;/p&gt;
&lt;p&gt;### Vulnerable Code
```php
public function deleteProcess(string $slug)
{
    $themeName = $slug;
    $activeTheme = setting(&amp;#39;App.siteTheme&amp;#39;);
    if ($activeTheme === $themeName) {
        return redirect()-&amp;gt;route(&amp;#39;templateSettings&amp;#39;)...;
    }&lt;/p&gt;
&lt;p&gt;$tablesToDrop = $this-&amp;gt;request-&amp;gt;getPost(&amp;#39;tables&amp;#39;);  // ← user-supplied, unvalidated
    if (!empty($tablesToDrop) &amp;amp;&amp;amp; is_array($tablesToDrop)) {
        $forge = \Config\Database::forge();
        $db    = \Config\Database::connect();
        foreach ($tablesToDrop as $table) {
            if ($db-&amp;gt;tableExists($table)) {
                $forge-&amp;gt;dropTable($table, true);  // ← no whitelist check
            }
        }
    }
```&lt;/p&gt;
&lt;p&gt;### PoC
1…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ci4-cms-erp/ci4ms&lt;/p&gt;
&lt;p&gt;### Summary
The `deleteProcess()` action accepts a POST parameter `tables[]` containing arbitrary table names. These are passed directly to `$forge-&amp;gt;dropTable()` without validating that the tables belong to the theme being deleted.&lt;/p&gt;
&lt;p&gt;The `deleteConfirm` view correctly populates `tables[]` from the theme&amp;#39;s own migration files, but the server-side `deleteProcess` does not verify the received values against those files. An authenticated admin can craft a POST request with arbitrary table names and drop any table in the database.&lt;/p&gt;
&lt;p&gt;This is a real bug even within the admin trust model: the action should be scoped to the theme&amp;#39;s own tables. The permission grants  delete this theme&amp;#39;s data&amp;#34;, not &amp;#34;drop any table&amp;#34;.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;### Location
`modules/Theme/Controllers/Theme.php` :: `deleteProcess()` ~line 147&lt;/p&gt;
&lt;p&gt;### Vulnerable Code
```php
public function deleteProcess(string $slug)
{
    $themeName = $slug;
    $activeTheme = setting(&amp;#39;App.siteTheme&amp;#39;);
    if ($activeTheme === $themeName) {
        return redirect()-&amp;gt;route(&amp;#39;templateSettings&amp;#39;)...;
    }&lt;/p&gt;
&lt;p&gt;$tablesToDrop = $this-&amp;gt;request-&amp;gt;getPost(&amp;#39;tables&amp;#39;);  // ← user-supplied, unvalidated
    if (!empty($tablesToDrop) &amp;amp;&amp;amp; is_array($tablesToDrop)) {
        $forge = \Config\Database::forge();
        $db    = \Config\Database::connect();
        foreach ($tablesToDrop as $table) {
            if ($db-&amp;gt;tableExists($table)) {
                $forge-&amp;gt;dropTable($table, true);  // ← no whitelist check
            }
        }
    }
```&lt;/p&gt;
&lt;p&gt;### PoC
1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vgrf-pr28-vf98</guid>
    </item>
  </channel>
</rss>
