Vulnerability record · CVE-2024-49754 · published 15 November 2024
CVE-2024-49754: LibreNMS API token field stored XSS
Librenms · Librenms
LibreNMS before 24.10.0 stores unsanitized input from the API token parameter on the API-Access page, allowing authenticated users to inject JavaScript that runs in other users' sessions. Because the payload persists and executes for anyone viewing the affected page, it can compromise accounts of higher-privileged users.
Description
LibreNMS is an open-source, PHP/MySQL/SNMP-based network monitoring system. 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. This vulnerability is fixed in 24.10.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Automated analysis
medium priorityStored XSS requires authentication and victim interaction, but the high EPSS score and public exploit reference raise the practical risk for exposed LibreNMS instances.
What it is
LibreNMS before 24.10.0 stores unsanitized input from the API token parameter on the API-Access page, allowing authenticated users to inject JavaScript that runs in other users' sessions. Because the payload persists and executes for anyone viewing the affected page, it can compromise accounts of higher-privileged users.
Impact
An attacker with a low-privileged account can run arbitrary JavaScript in the browser of any user who views the API-Access page, potentially stealing session data or performing actions as that user.
Attack surface
Reached over the network through the web interface by an authenticated user who creates an API token with a crafted token value; the victim must view the affected page, so user interaction is required.
Exploitation
Not listed in CISA KEV, but EPSS is high (0.71, 99th percentile) and a vendor advisory is tagged as an exploit reference, indicating public proof-of-concept or exploit detail exists.
What to do
- Upgrade LibreNMS to 24.10.0 or later, which contains the fix.
- If immediate upgrade is not possible, restrict access to the API-Access page to trusted administrators.
- Review and remove any suspicious existing API tokens with unexpected characters.
- Apply output encoding or input validation to the token parameter as a temporary compensating control.
Detection
- Search web server and application logs for API token creation requests containing script tags or event handlers in the token parameter.
- Audit existing API tokens for values containing HTML or JavaScript syntax.
- Monitor for anomalous authenticated sessions or actions originating from users who recently viewed the API-Access page.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2024-49754 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2024-49754), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.