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
GETproject_issues=javascript:alert(document.cookie)
Suggestion
It is recommended to filter dangerous protocols, e.g. javascript:/file:.
Impact
XSS vulnerabilities allow attackers to execute malicious scripts in users' browsers, enabling unauthorized access to sensitive data, session hijacking, or malware distribution.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-62365? CVE-2025-62365 is a medium-severity cross-site scripting (XSS) vulnerability in librenms/librenms (composer), affecting versions <= 25.6.0. It is fixed in 25.7.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of librenms/librenms are affected by CVE-2025-62365? librenms/librenms (composer) versions <= 25.6.0 is affected.
- Is there a fix for CVE-2025-62365? Yes. CVE-2025-62365 is fixed in 25.7.0. Upgrade to this version or later.
- Is CVE-2025-62365 exploitable, and should I be worried? Whether CVE-2025-62365 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-62365 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-62365? Upgrade
librenms/librenmsto 25.7.0 or later.