CVE-2020-15875: SQL Injection

Published Sep 13, 2026
·
Updated

An issue was discovered in LibreNMS 1.65. A remote authenticated attacker with normal privileges can extract all the information from the LibreNMS database via a SQL injection in the searchPhrase parameter in the /ajaxtable.php API endpoint. This affects as-selection.inc.php, edit-ports.inc.php, alertlog-stats.inc.php, alerts.inc.php, eventlog.inc.php, inventory.inc.php, ix-list.inc.php, ix-peers.inc.php, mempool-edit.inc.php, mempool.inc.php, poll-log.inc.php, processor-edit.inc.php, processor.inc.php, routing-edit.inc.php, sensors-common.inc.php, storage-edit.inc.php, storage.inc.php, and toner.inc.php (in includes/html/table). NOTE: some sources refer to this as CVE-2020-15876, but CVE-2020-15875 is the only correct CVE ID.

Affected Software

1 affected component
librenms librenms=1.65

Event History

Sep 13, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What level of access does an attacker need to exploit this issue?

The attacker must be remotely authenticated to LibreNMS with normal user privileges. No user interaction is required, and the attack can be performed over the network.

2

What information could be exposed?

Successful SQL injection through the searchPhrase parameter can allow the attacker to extract all information from the LibreNMS database. The stated impact is confidentiality loss; integrity and availability impacts are not identified.

3

Which endpoint and components are affected?

The injection is in the searchPhrase parameter of the /ajax_table.php API endpoint. It affects multiple table handlers under includes/html/table, including alert, event log, inventory, interface, memory pool, processor, routing, sensor, storage, and toner-related handlers.

4

What version should be used to remediate the issue?

The provided references include the comparison from LibreNMS 1.65 to 1.65.1 and the 1.65.1 release. Updating from the affected 1.65 release to 1.65.1 addresses the issue.

5

Which CVE identifier should be used for tracking?

Use CVE-2020-15875. Although some sources reportedly refer to CVE-2020-15876, the provided information states that CVE-2020-15875 is the only correct identifier.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203