CVE-2020-36862
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 · uneditedNagios XI versions prior to 5.6.11 contain unauthenticated vulnerabilities in the Highcharts local exporting tool. Crafted export requests could (1) inject script into exported/returned content due to insufficient output encoding (XSS), and (2) cause the server to fetch attacker-specified URLs (SSRF), potentially accessing internal network resources. An unauthenticated remote attacker can leverage these issues to execute script in a user's browser when the exported content is viewed and to disclose sensitive information reachable from the export server via SSRF.
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 confidenceNagios XI versions prior to 5.6.11 contain unauthenticated vulnerabilities in the Highcharts local exporting tool. The first vulnerability is a reflected XSS due to insufficient output encoding, allowing script injection into exported content viewed by users. The second is an SSRF vulnerability enabling the server to fetch attacker-specified URLs, potentially accessing internal network resources.
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< 5.6.11CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Nagios XI installation and versionLocate the Nagios XI installation directory and find the version file or check the Nagios XI admin interface for version information. Typical locations include /usr/local/nagiosxi or checking the About page in the web interface.Affected if The installed version is below 5.6.11
-
Compare version to affected rangeTake the discovered version number and compare it against the vulnerable range: any version prior to 5.6.11 is affected.Affected if Version is less than 5.6.11
-
Determine if Highcharts local exporting is enabledCheck the Nagios XI configuration files and settings for the Highcharts export feature. This is typically found in the Nagios XI web interface under the reporting or charting settings, or in configuration files related to the Highcharts module.Affected if The Highcharts local exporting feature is enabled and the version is below 5.6.11
-
Inspect network logs for unusual outbound requestsReview server access logs and network traffic for unexpected GET or POST requests from the Nagios XI server to external or internal URLs, which could indicate SSRF exploitation attempts.Affected if Unexpected outbound requests from the server are present and the version is below 5.6.11 with Highcharts exporting enabled
You are affected if your Nagios XI version is prior to 5.6.11 and the Highcharts local exporting feature is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.6.11
Upgrade Nagios XI to version 5.6.11 or later to patch both vulnerabilities. If upgrading is not immediately feasible, disable the Highcharts local exporting feature and review network segmentation to limit internal resource exposure from the server.
Nagios XI version 5.6.11 or later
- 1. Back up the current Nagios XI installation and database before proceeding with any upgrade.
- 2. Obtain the Nagios XI 5.6.11 or later version from the official Nagios website (www.nagios.com).
- 3. Follow the official Nagios XI upgrade documentation to apply the update, ensuring all prerequisites are met.
- 4. After upgrade, verify the Highcharts exporting functionality works correctly and the vulnerability is remediated.
- 5. Consider running a security scan or penetration test to confirm the XSS and SSRF vulnerabilities are no longer present.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36862 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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