<?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 14:15:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292767</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292767</link>
      <description>EUVD-2026-292767</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292767</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41228</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41228</link>
      <description>&lt;p&gt;Froxlor is open source server administration software. Prior to version 2.3.6, the Froxlor API endpoint `Customers.update` (and `Admins.update`) does not validate the `def_language` parameter against the list of available language files. An authenticated customer can set `def_language` to a path traversal payload (e.g., `../../../../../var/customers/webs/customer1/evil`), which is stored in the database. On subsequent requests, `Language::loadLanguage()` constructs a file path using this value and executes it via `require`, achieving arbitrary PHP code execution as the web server user. Version 2.3.6 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Froxlor is open source server administration software. Prior to version 2.3.6, the Froxlor API endpoint `Customers.update` (and `Admins.update`) does not validate the `def_language` parameter against the list of available language files. An authenticated customer can set `def_language` to a path traversal payload (e.g., `../../../../../var/customers/webs/customer1/evil`), which is stored in the database. On subsequent requests, `Language::loadLanguage()` constructs a file path using this value and executes it via `require`, achieving arbitrary PHP code execution as the web server user. Version 2.3.6 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41228</guid>
    </item>
    <item>
      <title>GHSA-w59f-67xm-rxx7 — Froxlor has Local File Inclusion via path traversal in API `def_language` parameter leads to Remote Code Execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w59f-67xm-rxx7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: froxlor/froxlor&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Froxlor API endpoint `Customers.update` (and `Admins.update`) does not validate the `def_language` parameter against the list of available language files. An authenticated customer can set `def_language` to a path traversal payload (e.g., `../../../../../var/customers/webs/customer1/evil`), which is stored in the database. On subsequent requests, `Language::loadLanguage()` constructs a file path using this value and executes it via `require`, achieving arbitrary PHP code execution as the web server user.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;**Root cause:** The API and web UI have inconsistent validation for the `def_language` parameter.&lt;/p&gt;
&lt;p&gt;The **web UI** (`customer_index.php:261`, `admin_index.php:265`) correctly validates `def_language` against `Language::getLanguages()`, which scans the `lng/` directory for actual language files:&lt;/p&gt;
&lt;p&gt;```php
// customer_index.php:260-265
$def_language = Validate::validate(Request::post(&amp;#39;def_language&amp;#39;), &amp;#39;default language&amp;#39;);
if (isset($languages[$def_language])) {
    Customers::getLocal($userinfo, [
        &amp;#39;id&amp;#39; =&amp;gt; $userinfo[&amp;#39;customerid&amp;#39;],
        &amp;#39;def_language&amp;#39; =&amp;gt; $def_language
    ])-&amp;gt;update();
```&lt;/p&gt;
&lt;p&gt;The **API** (`Customers.php:1207`, `Admins.php:600`) only runs `Validate::validate()` with the default regex `/^[^\r\n\t\f\0]*$/D`, which permits path traversal sequences:&lt;/p&gt;
&lt;p&gt;```php
// Customers.php:1167-1172 (customer branch)
} else {
    // allowed parameters
    $def_language = $this-&amp;gt;getParam(&amp;#39;def_language&amp;#39;, true, $result[&amp;#39;def_language&amp;#39;]);
    ...
}
// Cu…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: froxlor/froxlor&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Froxlor API endpoint `Customers.update` (and `Admins.update`) does not validate the `def_language` parameter against the list of available language files. An authenticated customer can set `def_language` to a path traversal payload (e.g., `../../../../../var/customers/webs/customer1/evil`), which is stored in the database. On subsequent requests, `Language::loadLanguage()` constructs a file path using this value and executes it via `require`, achieving arbitrary PHP code execution as the web server user.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;**Root cause:** The API and web UI have inconsistent validation for the `def_language` parameter.&lt;/p&gt;
&lt;p&gt;The **web UI** (`customer_index.php:261`, `admin_index.php:265`) correctly validates `def_language` against `Language::getLanguages()`, which scans the `lng/` directory for actual language files:&lt;/p&gt;
&lt;p&gt;```php
// customer_index.php:260-265
$def_language = Validate::validate(Request::post(&amp;#39;def_language&amp;#39;), &amp;#39;default language&amp;#39;);
if (isset($languages[$def_language])) {
    Customers::getLocal($userinfo, [
        &amp;#39;id&amp;#39; =&amp;gt; $userinfo[&amp;#39;customerid&amp;#39;],
        &amp;#39;def_language&amp;#39; =&amp;gt; $def_language
    ])-&amp;gt;update();
```&lt;/p&gt;
&lt;p&gt;The **API** (`Customers.php:1207`, `Admins.php:600`) only runs `Validate::validate()` with the default regex `/^[^\r\n\t\f\0]*$/D`, which permits path traversal sequences:&lt;/p&gt;
&lt;p&gt;```php
// Customers.php:1167-1172 (customer branch)
} else {
    // allowed parameters
    $def_language = $this-&amp;gt;getParam(&amp;#39;def_language&amp;#39;, true, $result[&amp;#39;def_language&amp;#39;]);
    ...
}
// Cu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w59f-67xm-rxx7</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1124 — Froxlor: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1124</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Froxlor ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Froxlor ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1124</guid>
    </item>
  </channel>
</rss>
