GHSA-VXQ6-8CWM-WJ99

Vulnerability from github – Published: 2025-08-18 22:25 – Updated: 2025-08-18 22:25
VLAI?
Summary
LibreNMS allows stored XSS in Alert Template name field
Details

Summary

A stored Cross-Site Scripting (XSS) vulnerability exists in LibreNMS (<= 25.6.0) in the Alert Template creation feature. This allows a user with the admin role to inject malicious JavaScript, which will be executed when the template is rendered, potentially compromising other admin accounts.


Details

In the LibreNMS web UI, when a user with the admin role visits /templates and clicks "Create new alert template", the "Template name" field fails to properly sanitize input. By inserting a payload like:

&lt;script>alert(document.cookie)&lt;/script> 

and filling the other fields with arbitrary content (e.g., test), once the template is saved, the script is executed. This confirms that user input is stored and later rendered without proper output encoding.

This vulnerability can be exploited for session hijacking, data theft, or other malicious actions targeting other admin users.


PoC

  1. Log in to LibreNMS using an account with the admin role.
  2. Navigate to: http://localhost:8000/templates.
  3. Click the "Create new alert template" button.
  4. Input the following into the Template name field:

&lt;script>alert(document.cookie)&lt;/script> 5. Fill the remaining fields (Template, Alert title, Recovery title) with arbitrary content such as test. 6. Click "Create template". 7. Upon saving, a JavaScript alert pops up, confirming the stored XSS is triggered. image


Impact

Type: Stored Cross-Site Scripting (XSS) Affected users: Only accounts with the admin role who access the Alert Templates page (http://localhost:8000/templates) are affected. Attackers need: Authenticated admin-level access.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "librenms/librenms"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "25.8.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-55296"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-08-18T22:25:29Z",
    "nvd_published_at": "2025-08-18T18:15:39Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\n\nA stored Cross-Site Scripting (XSS) vulnerability exists in LibreNMS (\u003c= 25.6.0) in the Alert Template creation feature. This allows a user with the **admin role** to inject malicious JavaScript, which will be executed when the template is rendered, potentially compromising other admin accounts.\n\n---\n### Details\n\nIn the LibreNMS web UI, when a user with the **admin role** visits `/templates` and clicks **\"Create new alert template\"**, the **\"Template name\"** field fails to properly sanitize input. By inserting a payload like:\n\n```\n\u0026lt;script\u003ealert(document.cookie)\u0026lt;/script\u003e \n```\n\nand filling the other fields with arbitrary content (e.g., `test`), once the template is saved, the script is executed. This confirms that user input is stored and later rendered without proper output encoding.\n\nThis vulnerability can be exploited for session hijacking, data theft, or other malicious actions targeting other admin users.\n\n---\n### PoC\n\n1. Log in to LibreNMS using an account with the **admin role**.\n2. Navigate to: `http://localhost:8000/templates`.\n3. Click the **\"Create new alert template\"** button.\n4. Input the following into the **Template name** field:\n\n   ```\n   \u0026lt;script\u003ealert(document.cookie)\u0026lt;/script\u003e\n   ```\n5. Fill the remaining fields (`Template`, `Alert title`, `Recovery title`) with arbitrary content such as `test`.\n6. Click **\"Create template\"**.\n7. Upon saving, a JavaScript alert pops up, confirming the stored XSS is triggered.\n\u003cimg width=\"1574\" height=\"848\" alt=\"image\" src=\"https://github.com/user-attachments/assets/bc482874-c47e-48e3-83b6-cb4a9dcf4a53\" /\u003e\n\n---\n### Impact\n\n **Type**: Stored Cross-Site Scripting (XSS)\n **Affected users**: Only accounts with the **admin role** who access the Alert Templates page (`http://localhost:8000/templates`) are affected.\n **Attackers need**: Authenticated admin-level access.",
  "id": "GHSA-vxq6-8cwm-wj99",
  "modified": "2025-08-18T22:25:29Z",
  "published": "2025-08-18T22:25:29Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/librenms/librenms/security/advisories/GHSA-vxq6-8cwm-wj99"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55296"
    },
    {
      "type": "WEB",
      "url": "https://github.com/librenms/librenms/commit/8ade3d827d317f5ac4b336617aafff865f825958"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/librenms/librenms"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "LibreNMS allows stored XSS in Alert Template name field"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…