<?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-06T21:52:24.625368+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-2025-62411</id>
    <title>fkie_cve-2025-62411</title>
    <updated>2026-10-06T21:52:24.627405+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>LibreNMS  is a community-based GPL-licensed network monitoring system. LibreNMS &lt;= 25.8.0 contains a Stored Cross-Site Scripting (XSS) vulnerability in the Alert Transports management functionality. When an administrator creates a new Alert Transport, the value of the Transport name field is stored and later rendered in the Transports column of the Alert Rules page without proper input validation or output encoding. This leads to arbitrary JavaScript execution in the admin’s browser. This vulnerability is fixed in 25.10.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2025-62411"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-frc6-pwgr-c28w</id>
    <title>GHSA-frc6-pwgr-c28w — LibreNMS has a Stored XSS vulnerability in its Alert Transport name field</title>
    <updated>2026-10-06T21:52:24.627524+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: librenms/librenms</p>
<p>### Summary</p>
<p>LibreNMS &lt;= 25.8.0 contains a **Stored Cross-Site Scripting (XSS)** vulnerability in the Alert Transports management functionality. When an administrator creates a new Alert Transport, the value of the `Transport name` field is stored and later rendered in the **Transports** column of the **Alert Rules** page without proper input validation or output encoding. This leads to arbitrary JavaScript execution in the admin’s browser.</p>
<p>### Details</p>
<p>* **Injection point:** `Transport name` field in `/alert-transports`.
* **Execution point:** **Transports** column in `/alert-rules`.
* **Scope:** Only administrators can create Alert Transports, and only administrators can view the affected Alert Rules page. Therefore, both exploitation and impact are limited to admin users.</p>
<p>### Steps to reproduce</p>
<p>1. Log in with an administrator account.
2. Navigate to:</p>
<p>```
   http://localhost:8000/alert-transports
   ```
3. Click **Create alert transport** and provide the following values:</p>
<p>* **Transport name:**</p>
<p>```html
     'onfocus='alert(1)' autofocus=
     ```
   * **Default Alert:** `ON`
   * **Email:** `test@gmail.com` (or any valid email)
   
    Save the transport.
   
4. Navigate to ```http://localhost:8000/alert-rules```. A popup `alert(1)` is triggered, confirming that the payload executes.
&lt;img width="1829" height="396" alt="image" src="https://github.com/user-attachments/assets/932ba17d-214d-4253-80b8-62539d1cfa28" /&gt;</p>
<p>### Impact</p>
<p>Only accounts with the admin ro…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-frc6-pwgr-c28w"/>
  </entry>
</feed>
