Skip to content

LibreNMS has a Stored XSS vulnerability in its Alert Transport name field

Moderate severity GitHub Reviewed Published Oct 16, 2025 in librenms/librenms • Updated Oct 16, 2025

Package

composer librenms/librenms (Composer)

Affected versions

< 25.10.0

Patched versions

25.10.0

Description

Summary

LibreNMS <= 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.

Details

  • 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.

Steps to reproduce

  1. Log in with an administrator account.

  2. Navigate to:

    http://localhost:8000/alert-transports
    
  3. Click Create alert transport and provide the following values:

    • Transport name:

      'onfocus='alert(1)' autofocus=
    • Default Alert: ON

    • Email: [email protected] (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.

image

Impact

Only accounts with the admin role who access the Alert Rules page (http://localhost:8000/alert-rules) are affected.

References

@murrant murrant published to librenms/librenms Oct 16, 2025
Published to the GitHub Advisory Database Oct 16, 2025
Reviewed Oct 16, 2025
Published by the National Vulnerability Database Oct 16, 2025
Last updated Oct 16, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(0th percentile)

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Learn more on MITRE.

CVE ID

CVE-2025-62411

GHSA ID

GHSA-frc6-pwgr-c28w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.