Medium

LibreNMS has Broken Access control on Graphs Feature

  • Disclosed: 17.11.2023
  • Updated: 11.10.2026 10:22

Summary

This vulnerability occurs when application is not checking access of each type of users as per their role and it autorizing the users to access any feature. When user access his Device dashboard in librenms, one request is going to graph.php to access image of graphs generated on the particular Device. This request can be accessed by lower privileged users as well and they can enumerate devices on librenms with their id or hostname.

Details

Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer.

PoC

  1. Login with Lower privilege user

  2. Go to /graph.php?width=150&height=45&device=1&type=device_ping_perf&from=1699022192&legend=no&bg=FFFFFF00&popup_title=ICMP+Response

  3. If its showing image with "device*ping_perf" which confirms that there is device with id 1

  4. Now you can change device parameter in above URL with hostname to check if that Hostname/IP exist or not like http://127.0.0.1:8000/graph.php?width=150&height=45&device=127.0.0.1&type=device_ping_perf&from=1699022192&legend=no&bg=FFFFFF00&popup_title=ICMP+Response

  5. If device hostname doesn't exist then it should show 500 error

Check attached screenshots for more info

Vulnerable code: https://github.com/librenms/librenms/blob/fa93034edd40c130c2ff00667ca2498d84be6e69/html/graph.php#L19C1-L25C2

Above is vulnerable line of code from Line number 19-25 This is not checking privilege of users to access any device hostname, its just checking if user is authenticated or not

Impact

Low privilege users can see all devices registered by admin users by using this method

Solution

Implement privilege access control feature to check if low privilege user have access or not.

Screenshots:-

<img width="967" alt="Screenshot 2023-11-04 at 8 31 15 PM" src="https://user-images.githubusercontent.com/31764504/281085588-1c5d81b9-83d7-4ba8-baf3-03c95a99cefe.png"> <img width="973" alt="Screenshot 2023-11-04 at 8 31 36 PM" src="https://user-images.githubusercontent.com/31764504/281085614-7a4d13b0-d316-4d24-bdd2-05c3a80ffd59.png"> <img width="955" alt="Screenshot 2023-11-04 at 8 31 48 PM" src="https://user-images.githubusercontent.com/31764504/281085629-43aa2b6f-7b18-415f-8001-519bda45f918.png">

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package librenms/librenms < 23.11.0 23.11.0

References

CVSS score 4.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-200
Platform
Composer
Package
librenms/librenms
Disclosed
17.11.2023
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-fpq5-4vwm-78x4 - CC BY 4.0

Vulnerability history: librenms/librenms

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (106) in the archive
Total entries
106
First → latest
10.2019 08.2026
Without a fix
6
Exploited in attacks
0

Severity breakdown

  • Critical 5
  • High 39
  • Medium 56
  • Low 6

Disclosures per year

  1. 2019: 6
  2. 2020: 0
  3. 2021: 7
  4. 2022: 26
  5. 2023: 12
  6. 2024: 24
  7. 2025: 15
  8. 2026: 16
Severity:
  1. High · 7.1 CVE-2026-84192 < 26.5.0 26.5.0
  2. High · 7.1 CVE-2020-36947 <= 1.46 no fix
  3. Critical · 9.1 CVE-2024-51092 < 24.10.0 24.10.0
  4. LibreNMS has Broken Access control on Graphs Feature this entry
    Medium · 4.3 CVE-2023-48294 < 23.11.0 23.11.0
  5. High · 7.8 CVE-2023-5591 < 23.10.0 23.10.0
  6. High · 8.4 CVE-2023-5060 < 23.9.1 23.9.1
  7. High · 7.6 CVE-2023-4347 < 23.8.0 23.8.0
  8. High · 8.8 CVE-2022-3525 < 22.10.0 22.10.0
  9. High · 7.6 CVE-2022-4068 < 22.10.0 22.10.0
  10. Critical · 9.8 CVE-2022-4070 < 22.10.0 22.10.0
  11. High CVE-2022-29712 < 22.4.0 22.4.0
  12. Critical · 9.8 CVE-2019-10665 <= 1.47 no fix
  13. Critical · 9.8 CVE-2018-20434 = 1.46 no fix
  14. High · 8.8 CVE-2018-20678 < 1.65 1.65
  15. High · 7.1 CVE-2022-0580 < 22.2.0 22.2.0
  16. High · 7.1 CVE-2022-0587 < 22.2.0 22.2.0
  17. Critical · 9.8 CVE-2021-44278 <= 21.11.0 no fix
  18. High · 8.8 CVE-2020-15877 < 1.65.1 1.65.1
Show more (5) Showing 40 of 45

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.