Advisory record · GHSA-72m9-7c8x-pmmw

LibreNMS uses Improper Sanitization on Service template name leads to Stored XSS

CVSS 7.1 HighCriticalEPSS 0.34 · 98th percentile

Critical, because:

  • CVSS score 7.1 (7.0 or more) and EPSS 0.34 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 22 Apr 2024, 18:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
librenms/librenmsPackagist<24.4.024.4.0
Identifiers
GHSA-72m9-7c8x-pmmw · CVE-2024-32479 · PKSA-g1ms-vbct-y8y2
Weakness (CWE)
CWE-79
Published
22 Apr 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

LibreNMS, the Packagist package librenms/librenms, is vulnerable in versions before 24.4.0. The service template name is not properly sanitized before it is placed into the delete button's onclick handler, so a crafted name can run attacker-supplied JavaScript in the browser of a user who views the template list and attempts a delete. The source describes this as stored cross-site scripting that could lead to cookie theft or other actions performed as the user. Upgrade to version 24.4.0 or later, which contains the fix.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.34, the 98th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:03 UTC First seen by agentprime
  2. 31 Oct 2026, 14:03 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.