Medium

LibreNMS has Stored Cross-site Scripting vulnerability in "Alert Transports" feature

  • Disclosed: 01.10.2024
  • Updated: 11.10.2026 10:22

Summary

A Stored Cross-Site Scripting (XSS) vulnerability in the "Alert Transports" feature allows authenticated users to inject arbitrary JavaScript through the "Details" section (which contains multiple fields depending on which transport is selected at that moment). This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Details

The vulnerability occurs when creating an alert transport. The application does not properly sanitize the user input in the "Details" field, allowing an attacker to inject and store arbitrary JavaScript. This script is then executed in the context of the page whenever the alert transport is viewed or processed.

For instance, the following payload can be used to trigger the XSS: test1<script>{onerror=alert}throw 1337</script>

When the page containing the transport details is loaded, this payload causes the browser to execute the injected script, which in this case triggers an alert popup.

The root cause of the vulnerability is that the application does not sanitize the value of $instance->displayDetails before appending it to the HTML output. This is demonstrated in the following code: https://github.com/librenms/librenms/blob/4777247327c793ed0a3306d0464b95176008177b/includes/html/print-alert-transports.php#L40

PoC

  1. Create a new alert transport in the LibreNMS interface.
  2. Depending on the transport chosen, just input the following payload in any field that ends up in the "Details" section: test1<script>{onerror=alert}throw 1337</script>
  3. Save the transport and trigger the alert.
  4. When the transport details are accessed, the injected script executes, displaying an alert popup.

Example Request:

http
POST /ajax_form.php HTTP/1.1
Host: <your_host>
X-Requested-With: XMLHttpRequest
X-CSRF-TOKEN: <your_XSRF_token>
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Cookie: <your_cookie>

_token=<your_token>&transport_id=2&type=alert-transports&name=Test1&transport-choice=canopsis-form&_token=Ep6belaqXe5qE301CGmtoOWJ71gvRfBXjRyhXEpH&transport-type=canopsis&canopsis-host=localhost%3Cscript%3E%7Bonerror%3Dalert%7Dthrow+1337%3C%2Fscript%3E&canopsis-port=5000&canopsis-user=%3Cscript%3E%7Bonerror%3Dalert%7Dthrow+1337%3C%2Fscript%3E&canopsis-pass=%3Cscript%3E%7Bonerror%3Dalert%7Dthrow+1337%3C%2Fscript%3E&canopsis-vhost=%3Cscript%3E%7Bonerror%3Dalert%7Dthrow+1337%3C%2Fscript%3E

Impact

It could allow authenticated users to execute arbitrary JavaScript code in the context of other users' sessions. Impacted users could have their accounts compromised, enabling the attacker to perform unauthorized actions on their behalf.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package librenms/librenms < 24.9.0 24.9.0

References

CVSS score 7.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:L
Weakness (CWE)
CWE-79
Platform
Composer
Package
librenms/librenms
Disclosed
01.10.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-7f84-28qh-9486 - CC BY 4.0

Vulnerability history: librenms/librenms

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (106) in the archive
Total entries
106
First → latest
10.2019 08.2026
Without a fix
6
Exploited in attacks
0

Severity breakdown

  • Critical 5
  • High 39
  • Medium 56
  • Low 6

Disclosures per year

  1. 2019: 6
  2. 2020: 0
  3. 2021: 7
  4. 2022: 26
  5. 2023: 12
  6. 2024: 24
  7. 2025: 15
  8. 2026: 16
Severity:
  1. High · 7.1 CVE-2026-84192 < 26.5.0 26.5.0
  2. High · 7.1 CVE-2020-36947 <= 1.46 no fix
  3. Critical · 9.1 CVE-2024-51092 < 24.10.0 24.10.0
  4. LibreNMS has Stored Cross-site Scripting vulnerability in "Alert Transports" feature this entry
    Medium · 7.5 CVE-2024-47523 < 24.9.0 24.9.0
  5. High · 7.8 CVE-2023-5591 < 23.10.0 23.10.0
  6. High · 8.4 CVE-2023-5060 < 23.9.1 23.9.1
  7. High · 7.6 CVE-2023-4347 < 23.8.0 23.8.0
  8. High · 8.8 CVE-2022-3525 < 22.10.0 22.10.0
  9. High · 7.6 CVE-2022-4068 < 22.10.0 22.10.0
  10. Critical · 9.8 CVE-2022-4070 < 22.10.0 22.10.0
  11. High CVE-2022-29712 < 22.4.0 22.4.0
  12. Critical · 9.8 CVE-2019-10665 <= 1.47 no fix
  13. Critical · 9.8 CVE-2018-20434 = 1.46 no fix
  14. High · 8.8 CVE-2018-20678 < 1.65 1.65
  15. High · 7.1 CVE-2022-0580 < 22.2.0 22.2.0
  16. High · 7.1 CVE-2022-0587 < 22.2.0 22.2.0
  17. Critical · 9.8 CVE-2021-44278 <= 21.11.0 no fix
  18. High · 8.8 CVE-2020-15877 < 1.65.1 1.65.1
Show more (5) Showing 40 of 45

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.