dbcve.org
Nagios XiApplication · Nagios

CVE-2021-47696

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 BPI config ID 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

Cross-site scripting (XSS) vulnerability in Nagios XI versions prior to 5.8.0 in the BPI (Business Process Intelligence) config ID parameter handling. User-supplied input for the BPI config ID is not properly validated or escaped before being rendered in the browser, allowing injection of arbitrary JavaScript in the context of a victim's session.

MitigationUpgrade to Nagios XI version 5.8.0 or later which includes proper input validation and output encoding for the BPI config ID parameter. If immediate upgrade is not possible, implement output encoding and input validation on all BPI-related parameters.

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. Check Nagios XI installation and version
    Locate the Nagios XI installation and determine the installed version. This is typically available in the web interface footer, or via command line tools like 'rpm -q nagiosxi' or 'dpkg -l nagiosxi' depending on the Linux distribution, or by checking the /usr/local/nagiosxi/etc/installation.ini file if it exists.
    Affected if The installed version of Nagios XI is prior to 5.8.0 (e.g., 5.7.x, 5.6.x, etc.)
  2. Verify BPI module is accessible
    Determine if the BPI (Business Process Intelligence) feature is enabled and accessible in the Nagios XI environment. This may involve checking if a user can navigate to the BPI section within the Nagios XI web interface, or checking for BPI-related files or configurations in the nagiosxi directory structure.
    Affected if The BPI module is installed and accessible to users in the Nagios XI environment, making the vulnerable config ID parameter reachable.
  3. Check for the BPI config ID parameter exposure
    Examine whether the BPI config ID parameter can be manipulated through web requests. In a test environment, access the BPI configuration interface and observe how the config ID parameter is handled when passed in URLs or form submissions.
    Affected if The BPI config ID parameter accepts user-supplied input that is reflected in the web interface without proper encoding, indicating the XSS vulnerability is present.

A user is affected if they are running Nagios XI version prior to 5.8.0 with the BPI module accessible, as the unvalidated BPI config ID parameter allows arbitrary JavaScript injection.

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 includes proper input validation and output encoding for the BPI config ID parameter. If immediate upgrade is not possible, implement output encoding and input validation on all BPI-related parameters.

Recommended fix Moderate confidence

Nagios XI 5.8.0

  1. Back up the current Nagios XI installation and database before upgrading
  2. Download Nagios XI 5.8.0 from the official Nagios website (www.nagios.com)
  3. Run the upgrade script or use the web-based upgrade interface to install version 5.8.0
  4. Verify the upgrade was successful by logging into the Nagios XI web interface
  5. Confirm the version number displays 5.8.0 after upgrade
Caveat Review Nagios XI 5.8.0 release notes for any new features or configuration changes that may affect your existing setup

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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