Medium

LibreNMS is vulnerable to Reflected-XSS in `report_this` function

  • Disclosed: 13.10.2025
  • Updated: 11.10.2026 10:22

Summary

Reflected-XSS in report_this function in librenms/includes/functions.php

Details

Recently, it was discovered that the report_this function had improper filtering (htmlentities function was incorrectly used in a href environment), which caused the project_issues parameter to trigger an XSS vulnerability.

The Vulnerable Sink: https://github.com/librenms/librenms/blob/master/includes/functions.php#L444

PoC

GET project_issues=javascript:alert(document.cookie)

Impact

XSS vulnerabilities allow attackers to execute malicious scripts in users' browsers, enabling unauthorized access to sensitive data, session hijacking, or malware distribution.

Suggestion

It is recommended to filter dangerous protocols, e.g. javascript:/file:.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package librenms/librenms < 25.7.0 25.7.0

References

CVSS score -
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P
Weakness (CWE)
CWE-79
Platform
Composer
Package
librenms/librenms
Disclosed
13.10.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-86rg-8hc8-v82p - 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. LibreNMS is vulnerable to Reflected-XSS in `report_this` function this entry
    Medium CVE-2025-62365 < 25.7.0 25.7.0
  4. Critical · 9.1 CVE-2024-51092 < 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.