# LibreNMS has Stored Cross-site Scripting vulnerability in "Alert Rules" feature

Advisory record · `GHSA-j2j9-7pr6-xqwv`

- **Identifiers:** `GHSA-j2j9-7pr6-xqwv` · `CVE-2024-47525` · `PKSA-8hhb-2cz5-4n8w`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 1 Oct 2024
- **Updated:** 1 Oct 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Oct 2024, 20:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 7.5 (7.0 or more) and EPSS 0.30 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `librenms/librenms` (Packagist): affected `<24.9.0`; fixed in `24.9.0`

## Machine-written summary

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

> LibreNMS versions before 24.9.0 have a stored cross-site scripting flaw in the Alert Rules feature, where the Title field is not sanitized. An authenticated user can create a rule with a crafted title that runs JavaScript in other users' browser sessions when the alert page loads, which can expose non-httponly cookies and allow actions on the victim's behalf. Upgrade to LibreNMS 24.9.0 or later.

Written 4 Nov 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.30, the 98th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j2j9-7pr6-xqwv)

## Sources

- [GitHub Advisory Database: GHSA-j2j9-7pr6-xqwv](https://github.com/advisories/GHSA-j2j9-7pr6-xqwv)
- [OSV: GHSA-j2j9-7pr6-xqwv](https://osv.dev/vulnerability/GHSA-j2j9-7pr6-xqwv)
- <https://github.com/librenms/librenms/security/advisories/GHSA-j2j9-7pr6-xqwv>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-47525>
- <https://github.com/librenms/librenms/commit/7620d220e48563938d869da7689b8ac3f7721490>
- <https://github.com/librenms/librenms>
- <https://github.com/librenms/librenms/blob/9455173edce6971777cf6666d540eeeaf6201920/includes/html/print-alert-rules.php#L405>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j2j9-7pr6-xqwv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j2j9-7pr6-xqwv/>. Everything for agents: <https://agentprime.io/llms.txt>.
