CVE-2024-32479

There is improper sanitization on Service template name which is reflecting in delete button onclick event. This value can be modified and crafted as any other javascript code.

Vulnerable Code

https://github.com/librenms/librenms/blob/a61c11db7e8ef6a437ab55741658be2be7d14d34/app/Http/Controllers/ServiceTemplateController.php#L67C23-L67C23

Above is vulnerable code line which needs to be properly sanitized

PoC

1. Go to /services/templates
2. Enter name as testing', '14', 'http://172.105.62.194:8000/services/templates/14');alert(1);//
3. Submit it and try to delete it, you will see popup

If you inspect element on delete button, you will notice this:-

Cross site scripting can lead to cookie stealing or an attacker can execute any other feature using this feature.

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.

CVE-2024-32479 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (24.4.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-32479? CVE-2024-32479 is a high-severity cross-site scripting (XSS) vulnerability in librenms/librenms (composer), affecting versions < 24.4.0. It is fixed in 24.4.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-32479? CVE-2024-32479 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of librenms/librenms are affected by CVE-2024-32479? librenms/librenms (composer) versions < 24.4.0 is affected.
4. Is there a fix for CVE-2024-32479? Yes. CVE-2024-32479 is fixed in 24.4.0. Upgrade to this version or later.
5. Is CVE-2024-32479 exploitable, and should I be worried? Whether CVE-2024-32479 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
6. What actually determines whether CVE-2024-32479 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.
7. How do I fix CVE-2024-32479? Upgrade librenms/librenms to 24.4.0 or later.