<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T07:48:52.654407+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-26992</id>
    <title>fkie_cve-2026-26992</title>
    <updated>2026-10-07T07:48:52.664386+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>LibreNMS is an auto-discovering PHP/MySQL/SNMP based network monitoring tool. In versions 26.1.1 and below, the port group name is not sanitized, allowing attackers with admin privileges to perform Stored Cross-Site Scripting (XSS) attacks. When a user adds a port group, an HTTP POST request is sent to the Request-URI "/port-groups". The name of the newly created port group is stored in the value of the name parameter. After the port group is created, the entry is displayed along with relevant buttons such as Edit and Delete. This issue has been fixed in version 26.2.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-26992"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-93fx-g747-695x</id>
    <title>GHSA-93fx-g747-695x — LibreNMS /port-groups name Stored Cross-Site Scripting</title>
    <updated>2026-10-07T07:48:52.664453+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: librenms/librenms</p>
<p>### Summary
**/port-groups name Stored Cross-Site Scripting**</p>
<p>- HTTP POST
- Request-URI(s): "/port-groups"
- Vulnerable parameter(s): "name"
- Attacker must be authenticated with "admin" privileges.
- When a user adds a port group, an HTTP POST request is sent to the Request-URI "/port-groups". The name of the newly created port group is stored in the value of the name parameter.
- After the port group is created, the entry is displayed along with some relevant buttons like Edit and Delete.</p>
<p>### Details
The vulnerability exists as the name of the port group is not sanitized of HTML/JavaScript-related characters
or strings. When the delete button is rendered, the following template is used to render the page:</p>
<p>_resources/views/port-group/index.blade.php:_
```
@extends('layouts.librenmsv1')
@section('title', __('Port Groups'))
@section('content')
&lt;div class="container-fluid"&gt;
&lt;x-panel id="manage-port-groups-panel"&gt;
// [...Truncated...]
@foreach($port_groups as $port_group)
// [...Truncated...]</p>
<p>&lt;button type="button" class="btn btn-danger btn-
sm" title="{{ __('delete Port Group') }}" aria-label="{{ __('Delete') }}"</p>
<p>onclick="delete_pg(this, '{{ $port_group-
&gt;name }}', '{{ route('port-groups.destroy', $port_group-&gt;id) }}')"&gt; // using the
port's name in the Delete button functionality without sanitizing for XSS related
characters/strings
```</p>
<p>As the device's name is not sanitized of HTML/JavaScript-related characters or strings, this can result in stored
cross-site scripting.…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-93fx-g747-695x"/>
  </entry>
</feed>
