# SQL Injection in librenms

Advisory record · `GHSA-h59f-p56g-g75v`

- **Identifiers:** `GHSA-h59f-p56g-g75v` · `CVE-2020-35700` · `PKSA-gp58-9bn9-hhyx`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 6 May 2021
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 May 2021, 18:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

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

## Machine-written summary

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

> LibreNMS versions before 21.1.0 are vulnerable to a second-order SQL injection in the Top Devices dashboard widget, through the sort_order parameter. An authenticated remote attacker can execute arbitrary SQL commands. Upgrade librenms/librenms to version 21.1.0 or later.

Written 5 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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 14:33 UTC: First seen by agentprime
- 31 Oct 2026, 14:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h59f-p56g-g75v)

## Sources

- [GitHub Advisory Database: GHSA-h59f-p56g-g75v](https://github.com/advisories/GHSA-h59f-p56g-g75v)
- [OSV: GHSA-h59f-p56g-g75v](https://osv.dev/vulnerability/GHSA-h59f-p56g-g75v)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-35700>
- <https://github.com/librenms/librenms/issues/12405>
- <https://github.com/librenms/librenms/pull/12422>
- <https://github.com/librenms/librenms/blob/master/app/Http/Controllers/Widgets/TopDevicesController.php>
- <https://github.com/librenms/librenms/releases/tag/21.1.0>
- <https://www.horizon3.ai/disclosures/librenms-second-order-sqli>

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-h59f-p56g-g75v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h59f-p56g-g75v/>. Everything for agents: <https://agentprime.io/llms.txt>.
