Advisory record · GHSA-jh57-j3vq-h438

LibreNMS vulnerable to a Time-Based Blind SQL injection leads to database extraction

CVSS 7.2 HighCriticalEPSS 0.20 · 97th percentile

Critical, because:

  • CVSS score 7.2 (7.0 or more) and EPSS 0.20 (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-jh57-j3vq-h438 · CVE-2024-32480 · PKSA-wskr-mbrz-ct8p
Weakness (CWE)
CWE-89
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.

GHSA-jh57-j3vq-h438 affects the LibreNMS Packagist package librenms/librenms in versions before 24.4.0. The "order" parameter of the list_devices API function is concatenated into an SQL statement without proper handling, which the source describes as a time-based blind SQL injection. An attacker who holds a valid API token with access to API functions could use it to extract the contents of the database. The package is fixed in 24.4.0, so upgrade to that version or later.

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.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.20, the 97th 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.