dbcve.org
Nagios XiApplication · Nagios

CVE-2020-36869

HIGH · 7.2 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.7.5 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.7.5 contain a SQL injection vulnerability in the SNMP Trap Interface edit 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.7.5 have a SQL injection vulnerability in the SNMP Trap Interface edit page. An authenticated administrator can supply specially crafted input that bypasses sanitization, enabling injection of malicious SQL statements into database queries.

MitigationUpgrade Nagios XI to version 5.7.5 or later to obtain the patched code that properly sanitizes SQL inputs 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.7.5

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. Confirm Nagios XI installation exists
    Look for Nagios XI installation directories, typically under /usr/local/nagiosxi/ or /opt/nagiosxi/. Check for nagiosxi subdirectories in common installation paths.
    Affected if Nagios XI is not installed or the installation directory cannot be found, the system is not affected by this CVE.
  2. Identify installed Nagios XI version
    Locate the version file or check via command line. Common locations include /usr/local/nagiosxi/version.txt or query the Nagios XI web interface for version information under the Admin > System Info section.
    Affected if The installed version is any version before 5.7.5 (e.g., 5.7.4, 5.7.3, 5.6.x, etc.).
  3. Verify SNMP Trap Interface component is present
    Check for the SNMP Trap Manager component in the Nagios XI installation. Look for trapd configuration files, snmptrapd daemon configs, or the SNMP Trap interface in the web UI under the 'Manage' or 'Configure' sections.
    Affected if The SNMP Trap Interface component is not installed or not present, the specific vulnerability path is not available.
  4. Check if authenticated administrator access is possible
    Review whether valid administrator credentials exist for the Nagios XI web interface. This CVE requires an authenticated administrator session to exploit the SQL injection.
    Affected if No valid administrator accounts exist or no web interface access is possible, exploitation would not be possible even on a vulnerable version.

A system is affected if Nagios XI version is below 5.7.5, the SNMP Trap Interface component is installed, and an authenticated administrator can access the web interface to reach the vulnerable edit page.

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.7.5 or later
Fixed in 5.7.5
Interim mitigation

Upgrade Nagios XI to version 5.7.5 or later to obtain the patched code that properly sanitizes SQL inputs in the SNMP Trap Interface.

Recommended fix High confidence

5.7.5

  1. 1. Back up the current Nagios XI installation and database before proceeding with any upgrade.
  2. 2. Download Nagios XI version 5.7.5 or later from the official Nagios website.
  3. 3. Run the upgrade installer following Nagios XI standard upgrade procedures.
  4. 4. Verify the upgrade completed successfully by logging into the Nagios XI web interface.
  5. 5. Confirm the SNMP Trap Interface edit page is accessible and functioning properly.

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

Fix this in Nagios Xi 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-2020-36869 — 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-36869 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