dbcve.org
LibrenmsApplication

CVE-2025-65013

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 25.11.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LibreNMS is an auto-discovering PHP/MySQL/SNMP based network monitoring tool. Prior to version 25.11.0, 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. This issue has been patched in version 25.11.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A reflected cross-site scripting (XSS) vulnerability exists in LibreNMS prior to version 25.11.0. The /maps/nodeimage endpoint reflects the Image Name parameter in the HTTP response without proper output encoding, allowing injection of arbitrary JavaScript via crafted URLs.

MitigationUpgrade to LibreNMS version 25.11.0 or later, which includes proper output encoding for the Image Name parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibrenmsApplication
Affected:< 25.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LibreNMS installation
    Locate the LibreNMS installation directory (common paths: /opt/librenms, /var/www/html/librenms, or check your web root). Look for the main index.php or composer.json file.
    Affected if LibreNMS is not installed on this system
  2. Determine installed LibreNMS version
    Check the version file or the composer.json in the LibreNMS directory. Common location: /opt/librenms/composer.json or /opt/librenms/.git/FETCH_HEAD. Compare the version against 25.11.0.
    Affected if The installed version is lower than 25.11.0 (e.g., 25.10.0, 25.9.0, etc.)
  3. Verify application is running
    Confirm the LibreNMS web application is accessible. Try accessing the main URL (e.g., http://your-server/librenms/ or https://your-server/). Check if the HTTP service is running.
    Affected if The LibreNMS web interface is accessible and running
  4. Confirm endpoint accessibility
    Attempt to access the /maps/nodeimage endpoint. This typically requires authentication, but the vulnerability exists in how the parameter is reflected in the response. Check if the route is registered in the application.
    Affected if The /maps/nodeimage endpoint exists and processes the Image Name parameter

You are affected if LibreNMS is installed with a version lower than 25.11.0 and the /maps/nodeimage endpoint is accessible in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.11.0 or later
Fixed in 25.11.0
Interim mitigation

Upgrade to LibreNMS version 25.11.0 or later, which includes proper output encoding for the Image Name parameter.

Recommended fix High confidence

25.11.0

  1. Upgrade LibreNMS to version 25.11.0 or later
  2. Verify the upgrade was successful by checking the LibreNMS version at /about page or via command line: ./lnms version
  3. Test that the /maps/nodeimage endpoint now properly encodes the Image Name parameter

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Librenms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65013 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data