dbcve.org
Nagios XiApplication · Nagios

CVE-2021-47697

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.8.0 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
Nagios XI versions prior to 5.8.0 are vulnerable to cross-site scripting (XSS) via the Views feature URL handling. 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 · moderate confidence

Nagios XI versions prior to 5.8.0 contain a stored cross-site scripting (XSS) vulnerability in the Views feature. The application fails to properly validate or escape user-supplied input when handling URLs, allowing an attacker to inject malicious JavaScript that executes in the context of a victim's browser when the crafted content is rendered.

MitigationUpgrade to Nagios XI version 5.8.0 or later, which contains the fix for this XSS vulnerability in the Views feature.

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

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 admin interface and navigate to Admin > System Information, or check the /usr/local/nagiosxi/etc/styles/optional.php version file if accessible, or run: cat /usr/local/nagiosxi/etc/xi-version.php
    Affected if The displayed version number is less than 5.8.0 (for example, 5.7.x, 5.6.x, etc.)
  2. Confirm Views feature is in use
    Log into Nagios XI and navigate to Home > Views, or check if any custom views have been created by examining the database or xi_views table
    Affected if The Views feature is actively used and contains or may contain custom views with URL fields
  3. Inspect stored Views for URL content
    Access the Views configuration panel and examine each view's URL field settings, or query the database for entries in xi_views that contain URL parameters
    Affected if Any stored views contain URL parameters that were not validated or may contain unsanitized user-supplied input
  4. Check for injected JavaScript patterns
    Review the source HTML of rendered Views pages in a browser or via curl to inspect if URL parameters are properly escaped or if script tags appear in the rendered output
    Affected if Raw script tags, javascript: protocols, or unescaped HTML special characters appear in the rendered URL content

You are affected if Nagios XI is installed with a version prior to 5.8.0 AND the Views feature is configured with stored content containing URL fields that may render unescaped JavaScript.

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.8.0 or later
Fixed in 5.8.0
Interim mitigation

Upgrade to Nagios XI version 5.8.0 or later, which contains the fix for this XSS vulnerability in the Views feature.

Recommended fix High confidence

5.8.0

  1. Backup your current Nagios XI installation and database before proceeding with any upgrade
  2. Download Nagios XI version 5.8.0 or later from the official Nagios website (www.nagios.com)
  3. Run the official Nagios XI upgrade installer for version 5.8.0
  4. After upgrade completes, verify the Nagios XI services are running correctly
  5. Test the Views feature to confirm XSS vulnerability is remediated
Caveat Review Nagios XI 5.8.0 release notes for any configuration or feature changes that may affect your existing setup before upgrading

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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