dbcve.org
Nagios XiApplication · Nagios

CVE-2020-36860

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.7.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Core Config Manager (CCM) in Nagios XI versions prior to CCM 3.0.7 / Nagios XI 5.7.4 contains multiple cross-site scripting (XSS) vulnerabilities in the object edit pages. Insufficient validation or escaping of user-supplied input may allow an attacker to inject and execute arbitrary script in the context of a victim's browser.

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 Core Config Manager (CCM) versions prior to 3.0.7 (or XI prior to 5.7.4) contain multiple stored XSS vulnerabilities in object edit pages. User-supplied input in these pages is insufficiently validated or escaped, allowing attackers to inject malicious JavaScript that executes in the context of other users' browsers.

MitigationUpgrade Nagios XI to version 5.7.4 or later (CCM to 3.0.7 or later) to obtain the patched component. Alternatively, implement output encoding and input validation on object edit pages as a compensating control.

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.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 version
    Access the Nagios XI administration interface and navigate to the About or System Information page, typically found under the Admin or Settings menu. Alternatively, check the /usr/local/nagiosxi/etc/buildinfo file or run the command 'cat /usr/local/nagiosxi/etc/buildinfo' via SSH if you have server access.
    Affected if The installed version is lower than 5.7.4 (or the CCM version is lower than 3.0.7 if shown separately).
  2. Confirm CCM component is active
    Log into the Nagios XI web interface and verify that the Core Config Manager (CCM) module is accessible. CCM is typically accessed via the 'Configure' menu or directly at /nagiosxi/ccm/. Attempt to navigate to the object configuration pages within CCM.
    Affected if The CCM interface is accessible and allows editing of Nagios objects (hosts, services, contacts, etc.).
  3. Check CCM object edit functionality
    Within the CCM interface, navigate to any object edit page such as host configuration, service configuration, or contact configuration. These are found under the 'Monitoring' or 'Configure' sections within CCM.
    Affected if The object edit pages are reachable and allow input of custom values into fields such as host names, service descriptions, or contact information.

A user is affected if their Nagios XI installation is version 5.7.3 or earlier AND the Core Config Manager component is active and accessible for object configuration.

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.4 or later
Fixed in 5.7.4
Interim mitigation

Upgrade Nagios XI to version 5.7.4 or later (CCM to 3.0.7 or later) to obtain the patched component. Alternatively, implement output encoding and input validation on object edit pages as a compensating control.

Recommended fix High confidence

Nagios XI 5.7.4 (or CCM 3.0.7)

  1. 1. Back up the current Nagios XI installation and database before upgrading
  2. 2. Upgrade to Nagios XI 5.7.4 or later (which includes CCM 3.0.7)
  3. 3. Alternatively, upgrade the Core Config Manager (CCM) component to version 3.0.7 or later
  4. 4. After upgrade, verify the CCM version shows 3.0.7 or higher in the Nagios XI interface
  5. 5. Test that the object edit pages properly sanitize input and no longer allow XSS injection

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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