dbcve.org
Nagios XiApplication · Nagios

CVE-2020-36857

HIGH · 7.2 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.6.14 or later.
See remediation →
78/100
Remediation priority · High
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
Nagios XI versions prior to 5.6.14 contain a post-authentication SQL injection vulnerability in the SNMP Trap Interface page. Exploitation requires an account with administrative privileges to access the affected interface. A user with administrative access could supply crafted input that is not properly sanitized, allowing SQL injection that may lead to unauthorized disclosure or modification of application data or execution of arbitrary SQL commands against the backend database.

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

Nagios XI versions before 5.6.14 contain a post-authentication SQL injection vulnerability in the SNMP Trap Interface page. An attacker with administrative privileges can supply crafted input that is not properly sanitized, allowing injection of arbitrary SQL commands into backend database queries.

MitigationUpgrade Nagios XI to version 5.6.14 or later to obtain the patched code that properly sanitizes input in the SNMP Trap Interface.

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
Nagios XiApplication
Affected:< 5.6.14

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 Nagios XI installation and version
    Locate the Nagios XI installation directory and check the version file or use the web interface version display to determine the installed version number
    Affected if The installed version is lower than 5.6.14
  2. Verify SNMP Trap Interface is enabled
    Access the Nagios XI web interface and navigate to the SNMP Trap Interface configuration page to determine if this feature is currently active or configured
    Affected if The SNMP Trap Interface feature is enabled or has been configured in the system
  3. Confirm administrative access exists
    Check if an administrative user account with privileges to access the SNMP Trap Interface exists in the Nagios XI system
    Affected if An administrative user account with access to the SNMP Trap Interface page is present in the system

The system is affected by this CVE if Nagios XI version is below 5.6.14 AND the SNMP Trap Interface is enabled and accessible with administrative credentials.

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.

dbcve · scoped
Upgrade available Upgrade to 5.6.14 or later
Fixed in 5.6.14
Interim mitigation

Upgrade Nagios XI to version 5.6.14 or later to obtain the patched code that properly sanitizes input in the SNMP Trap Interface.

Recommended fix High confidence

Nagios Xi 5.6.14 or later

  1. Back up the Nagios XI system database and configuration files before starting the upgrade process
  2. Download Nagios XI version 5.6.14 or later from the official Nagios website (www.nagios.com)
  3. Run the Nagios XI upgrade script or use the web-based upgrade interface to apply the update
  4. Restart the Nagios services to ensure all components load the updated code
  5. Log in to the Nagios XI web interface and navigate to the SNMP Trap Interface to verify the page functions correctly
  6. Confirm the upgrade was successful by checking the Nagios XI version in the Admin > System Information section
Caveat Test all administrative functionality, especially the SNMP Trap Interface, after upgrading to ensure no regression in features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-36857 — 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-2020-36857 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