LibreNMS has a Persistent XSS from Insecure Input Sanitization Affects Multiple EndpointsGHSA-4m5r-w2rq-q54q
HIGHFix: librenms/librenms@bb47314GHSA-4m5r-w2rq-q54q is a high-severity (CVSS 7.2) Cross-site Scripting (XSS) vulnerability in librenms/librenms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for librenms/librenms — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4m5r-w2rq-q54q.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
librenms/librenmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The application fail to sanitising inputs properly and rendering the code from user input to browser which allow an attacker to execute malicious javascript code.
Details
User with Admin role can edit the Display Name of a device, the application did not properly sanitize the user input in the device Display Name, if java script code is inside the name of the device Display Name, its can be trigger from different sources.
PoC
- Use an Admin role user to change the Display Name of a device into the payload
<img src="x" onerror="alert(document.cookie)">
2.1. Go to manage user and choose Manage Access
2.2. A pop-up will show
3.1. Create a new Alert Rule where it will check if the device is up or down by using ICMP and then add the rule to the device.
3.2. Once the device is down, there will be an alert in the Alerts Notifications
3.3. Hover over the Hostname will see a pop-up.
4.1. The same can be trigger in the Alert History once hover over the Device field.
5.1. The same can be trigger once hover over the Hostname field from the Event Log of the device.
6.1. The same can be trigger in the Outages function in the Logs of the device.
7.1. In the Active Alerts of the device.
8.2. In the Alert History of the device.
9.1. They can also be trigger in the dashboard.
10.1. Also if change the payload into <img src="x" onerror="alert(document['cookie'])">, it can also be trigger in the Availability Map.
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | librenms/librenms | all versions | 24.10.0composer require librenms/librenms:^24.10.0 |
Affected Products
librenmslibrenmsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for librenms/librenms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update librenms/librenms to 24.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4m5r-w2rq-q54q is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-4m5r-w2rq-q54q in your dependencies?
Find it across Packagist, including transitive dependencies.