dbcve.org
LibrenmsApplication

CVE-2018-20678

HIGH · 8.8 CVSS v3.0 Published 2019-03-28
Fix available
A fix is available. Upgrade to after 1.47 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LibreNMS through 1.47 allows SQL injection via the html/ajax_table.php sort[hostname] parameter, exploitable by authenticated users during a search.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in LibreNMS through version 1.47 in the html/ajax_table.php script. The sort[hostname] parameter during search operations does not properly sanitize user input, allowing authenticated users to inject arbitrary SQL queries.

MitigationUpgrade LibreNMS to a patched version beyond 1.47, or implement proper input validation and parameterized queries in ajax_table.php to prevent SQL injection in the sort parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibrenmsApplication
Affected:<= 1.47

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed LibreNMS version
    Locate the version file or check the web interface footer for the LibreNMS version number. Common locations include includes/constants.php or the admin dashboard.
    Affected if The installed version is 1.47 or lower.
  2. Verify ajax_table.php exists
    Check if the file html/ajax_table.php exists in the LibreNMS installation directory.
    Affected if The file exists and the application is version 1.47 or lower.
  3. Confirm authentication is enabled
    Check the LibreNMS configuration for user authentication settings. Verify that the application requires login for access.
    Affected if Authentication is enabled and users can access search functionality in the web interface.
  4. Review access logs for ajax_table.php usage
    Examine web server access logs for requests to html/ajax_table.php containing the sort[hostname] parameter, which indicates the vulnerable code path is being exercised.
    Affected if Requests to ajax_table.php with sort parameter are being logged from authenticated users.

A user is affected if running LibreNMS version 1.47 or lower with authentication enabled and the ajax_table.php script accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.47
Interim mitigation

Upgrade LibreNMS to a patched version beyond 1.47, or implement proper input validation and parameterized queries in ajax_table.php to prevent SQL injection in the sort parameter.

Fix this in Librenms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-20678 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-20678 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data