GHSA-j8cq-7f6p-256x — librenms/librenms
MEDIUMGHSA-j8cq-7f6p-256x is a medium-severity (CVSS 6.2) vulnerability in librenms/librenms. A fix is available for librenms/librenms — see the affected versions and patch details below.
LibreNMS vulnerable to Reflected Cross-Site Scripting (XSS) in endpoint `/maps/nodeimage` parameter `Image Name`
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-j8cq-7f6p-256x.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-j8cq-7f6p-256x plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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
A Reflected Cross-Site Scripting (XSS) vulnerability was identified in the LibreNMS application at the /maps/nodeimage endpoint. The Image Name parameter is reflected in the HTTP response without proper output encoding or sanitization, allowing an attacker to craft a URL that, when visited by a victim, causes arbitrary JavaScript execution in the victim’s browser.
Details
-
Vulnerable Endpoint:
GET /maps/nodeimage -
Parameter:
Image Name(reflected in response) -
Vulnerability type: Reflected Cross-Site Scripting (XSS) — input is reflected in server response and executed in victim browser.
-
CWE: CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-site Scripting)
Description
The application takes the value of the Image Name parameter from a request to /maps/nodeimage and includes it in the generated page or response without proper contextual encoding. Because the input is reflected immediately back to the client and parsed as HTML/JavaScript by the browser, an attacker can craft a URL containing a malicious script. If a victim (for example, an authenticated user or administrator) is tricked into visiting that URL, the injected script will execute in the victim’s browser context.
Proof of Concept (PoC)
Construct a request that includes the following payload in the Image Name parameter. The payload below should be used exactly as provided:
<script>alert('PoC-XXS51')</script>
Steps to reproduce
-
Authenticate as any user allowed to manage Node Images;
-
Navigate the endpoint '/maps/nodeimage' and click on "New Image". Choose any valide image and, on
Image Nameparameter, insert the payload above .
- Observe the server response page; if vulnerable, the payload will be executed by the browser and an alert box with
PoC-XXS51will appear.
Observed behavior
The supplied payload is reflected in the HTTP response and interpreted by the browser, resulting in immediate execution (demonstrated by an alert popup). This confirms the application does not perform appropriate output encoding for the Image Name parameter.
Impact
Reflected XSS can be used to:
-
Execute arbitrary JavaScript in the context of any user who visits the crafted link.
-
Steal session cookies or authentication tokens (leading to session hijacking).
-
Perform actions on behalf of the victim (CSRF-like actions executed via script).
-
Phish users by manipulating the page UI, or exfiltrate sensitive information visible to the victim.
-
Pivot to further attacks depending on application context and user privileges.
References
-
CWE-79 — Cross-Site Scripting (XSS).
-
OWASP XSS Prevention Cheat Sheet.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | librenms/librenms | all versions | 25.11.0composer require librenms/librenms:^25.11.0 |
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 25.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8cq-7f6p-256x 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j8cq-7f6p-256x can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j8cq-7f6p-256x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j8cq-7f6p-256x in your dependencies?
O3 Security finds GHSA-j8cq-7f6p-256x across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.