dbcve.org
Nagios XiApplication · Nagios

CVE-2020-36861

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.7.5 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.8 / Nagios XI 5.7.5 contains multiple cross-site scripting (XSS) vulnerabilities in the overlay UI elements and the Notification/Check Period 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.8/5.7.5 contain multiple stored XSS vulnerabilities in overlay UI elements and Notification/Check Period pages. Insufficient input validation allows attackers to inject malicious JavaScript that executes in victim browsers when these pages are rendered.

MitigationUpgrade to Nagios XI 5.7.5 or CCM 3.0.8 or later which implements proper input validation and output encoding. Review existing CCM installations for any injected malicious scripts.

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
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. Check Nagios XI version
    Log into the Nagios XI web interface and navigate to the Admin > System Information page, or run 'cat /usr/local/nagiosxi/etc/xi-sys.cfg' from the server command line to find the installed version number.
    Affected if The version shown is less than 5.7.5 (or CCM version is less than 3.0.8)
  2. Confirm Core Config Manager (CCM) is enabled
    Access the CCM interface by logging into Nagios XI and navigating to the Config > Core Config Manager menu, or attempt to access /nagiosxi/ccm/ directly.
    Affected if The CCM interface loads and is accessible to your user account
  3. Identify Notification period configurations
    In the CCM, go to General > Notification Periods and review any configured notification period objects for any injected JavaScript in fields such as name, alias, or timeperiod definitions.
    Affected if Malicious script tags or suspicious JavaScript code are present in any Notification Period configuration fields
  4. Identify Check period configurations
    In the CCM, go to General > Check Periods and review any configured check period objects for any injected JavaScript in fields such as name, alias, or timeperiod definitions.
    Affected if Malicious script tags or suspicious JavaScript code are present in any Check Period configuration fields
  5. Review overlay UI elements
    Navigate through the CCM interface and inspect any overlay dialogs or modal windows that render user-supplied data, particularly those that display host or service configuration details.
    Affected if Overlay elements render unsanitized input that could execute JavaScript when opened

A user is affected if their Nagios XI installation is version 5.7.5 or earlier (or CCM 3.0.8 or earlier) AND they have access to the CCM interface where stored XSS payloads may exist in Notification Period, Check Period, or overlay configurations.

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 to Nagios XI 5.7.5 or CCM 3.0.8 or later which implements proper input validation and output encoding. Review existing CCM installations for any injected malicious scripts.

Recommended fix High confidence

Nagios XI 5.7.5 or later (CCM 3.0.8 or later)

  1. Backup your current Nagios XI installation and database before proceeding with the upgrade
  2. Download Nagios XI version 5.7.5 or later from the official Nagios website (www.nagios.com)
  3. Run the Nagios XI upgrade installer following the standard upgrade procedure
  4. After upgrade, verify the Core Config Manager (CCM) version is 3.0.8 or later
  5. Confirm the XSS vulnerabilities in CCM overlay UI elements and Notification/Check Period pages are resolved

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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