<?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>Sun, 04 Oct 2026 17:03:38 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325495</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325495</link>
      <description>EUVD-2026-325495</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325495</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41236</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41236</link>
      <description>&lt;p&gt;Froxlor is open source server administration software. Version 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized_keys` under a customer-controlled home directory without verifying that the target path is not a symbolic link. If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace `~/.ssh/authorized_keys` with a symlink to `/root/.ssh/authorized_keys`. When Froxlor&amp;#39;s privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root&amp;#39;s authorized key file, resulting in root SSH access. Version 2.3.7 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Froxlor is open source server administration software. Version 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized_keys` under a customer-controlled home directory without verifying that the target path is not a symbolic link. If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace `~/.ssh/authorized_keys` with a symlink to `/root/.ssh/authorized_keys`. When Froxlor&amp;#39;s privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root&amp;#39;s authorized key file, resulting in root SSH access. Version 2.3.7 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41236</guid>
    </item>
    <item>
      <title>GHSA-mq5v-pxpm-8jw2 — Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mq5v-pxpm-8jw2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: froxlor/froxlor&lt;/p&gt;
&lt;p&gt;### Summary
Froxlor 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized_keys` under a customer-controlled home directory without verifying that the target path is not a symbolic link.&lt;/p&gt;
&lt;p&gt;If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace `~/.ssh/authorized_keys` with a symlink to `/root/.ssh/authorized_keys`. When Froxlor&amp;#39;s privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root&amp;#39;s authorized key file, resulting in root SSH access.&lt;/p&gt;
&lt;p&gt;### Details
The customer-facing SSH key workflow accepts an FTP user selection and an arbitrary public key from the authenticated session and forwards them into `SshKeys::add()`:&lt;/p&gt;
&lt;p&gt;```php
// customer_ftp.php:251-253
if ($action == &amp;#39;add&amp;#39; &amp;amp;&amp;amp; Request::post(&amp;#39;send&amp;#39;) == &amp;#39;send&amp;#39;) {
    $result = $log-&amp;gt;logAction(USR_ACTION, LOG_INFO, &amp;#34;added SSH-key&amp;#34;);
    Commands::get()-&amp;gt;apiCall(&amp;#39;SshKeys.add&amp;#39;, Request::postAll());
}
```&lt;/p&gt;
&lt;p&gt;On the server side, the add handler stores the public key and schedules an NSS rebuild as long as the customer has shell capability enabled at the customer level:&lt;/p&gt;
&lt;p&gt;```php
// lib/Froxlor/Api/Commands/SshKeys.php:67-70,120-145
if ($this-&amp;gt;getUserDetail(&amp;#39;shell_allowed&amp;#39;) != &amp;#39;1&amp;#39;) {
    throw new Exception(&amp;#34;You cannot add SSH keys because shell access is disabled for your account.&amp;#34;);
}&lt;/p&gt;
&lt;p&gt;$ins_stmt…&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
Froxlor 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized_keys` under a customer-controlled home directory without verifying that the target path is not a symbolic link.&lt;/p&gt;
&lt;p&gt;If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace `~/.ssh/authorized_keys` with a symlink to `/root/.ssh/authorized_keys`. When Froxlor&amp;#39;s privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root&amp;#39;s authorized key file, resulting in root SSH access.&lt;/p&gt;
&lt;p&gt;### Details
The customer-facing SSH key workflow accepts an FTP user selection and an arbitrary public key from the authenticated session and forwards them into `SshKeys::add()`:&lt;/p&gt;
&lt;p&gt;```php
// customer_ftp.php:251-253
if ($action == &amp;#39;add&amp;#39; &amp;amp;&amp;amp; Request::post(&amp;#39;send&amp;#39;) == &amp;#39;send&amp;#39;) {
    $result = $log-&amp;gt;logAction(USR_ACTION, LOG_INFO, &amp;#34;added SSH-key&amp;#34;);
    Commands::get()-&amp;gt;apiCall(&amp;#39;SshKeys.add&amp;#39;, Request::postAll());
}
```&lt;/p&gt;
&lt;p&gt;On the server side, the add handler stores the public key and schedules an NSS rebuild as long as the customer has shell capability enabled at the customer level:&lt;/p&gt;
&lt;p&gt;```php
// lib/Froxlor/Api/Commands/SshKeys.php:67-70,120-145
if ($this-&amp;gt;getUserDetail(&amp;#39;shell_allowed&amp;#39;) != &amp;#39;1&amp;#39;) {
    throw new Exception(&amp;#34;You cannot add SSH keys because shell access is disabled for your account.&amp;#34;);
}&lt;/p&gt;
&lt;p&gt;$ins_stmt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mq5v-pxpm-8jw2</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1737 — Froxlor: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1737</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Froxlor ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Froxlor ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1737</guid>
    </item>
  </channel>
</rss>
