Summary
LibreNMS: SSRF-driven stored XSS via Oxidized API response fields in device showconfig page
The Oxidized integration URL (oxidized.url) is admin-configurable. LibreNMS fetches device info and version history from that URL and renders JSON fields (name, ip, model, author, commit message) into HTML without htmlspecialchars(). An admin pointing the URL at an attacker-controlled server achieves persistent XSS affecting all users who view any device's showconfig tab.
CVSS
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N, 8.1 High
Details
// includes/html/pages/device/showconfig.inc.php:276-278
echo '<li ...><strong>Node:</strong> ' . $node_info['name'] . '</li>';
echo '<li ...><strong>IP:</strong> ' . $node_info['ip'] . '</li>';
echo '<li ...><strong>Model:</strong> '. $node_info['model'] . '</li>';
// lines 349, 353: author and commit message also unescaped
Attack chain
- Admin sets
oxidized.urltohttp://attacker.example.com/. - Attacker server returns
{"name":"<img src=x onerror=alert(1)>","ip":"x","model":"x"}. - Any user viewing any device showconfig tab triggers the XSS.
PoC
Mock Oxidized server confirmed in response:
[!!!] CONFIRMED, ...<strong>Node:</strong> <img src=x onerror="alert('SSRF-XSS-oxidized')">...
Prerequisite
Admin session. Oxidized integration must be enabled.
Impact
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.
GHSA-7GWW-X7FH-JF9J has a CVSS score of 8.1 (High). The vector is network-reachable, high 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 (26.7.0); upgrading removes the vulnerable code path.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
echo '<li ...><strong>Node:</strong> ' . htmlspecialchars($node_info['name'], ENT_QUOTES, 'UTF-8') . '</li>';
Apply to all fields from $node_info, $author, $msg.
Frequently Asked Questions
- What is GHSA-7GWW-X7FH-JF9J? GHSA-7GWW-X7FH-JF9J is a high-severity cross-site scripting (XSS) vulnerability in librenms/librenms (composer), affecting versions < 26.7.0. It is fixed in 26.7.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is GHSA-7GWW-X7FH-JF9J? GHSA-7GWW-X7FH-JF9J has a CVSS score of 8.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.
- Which versions of librenms/librenms are affected by GHSA-7GWW-X7FH-JF9J? librenms/librenms (composer) versions < 26.7.0 is affected.
- Is there a fix for GHSA-7GWW-X7FH-JF9J? Yes. GHSA-7GWW-X7FH-JF9J is fixed in 26.7.0. Upgrade to this version or later.
- Is GHSA-7GWW-X7FH-JF9J exploitable, and should I be worried? Whether GHSA-7GWW-X7FH-JF9J 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 GHSA-7GWW-X7FH-JF9J 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 GHSA-7GWW-X7FH-JF9J? Upgrade
librenms/librenmsto 26.7.0 or later.