dbcve.org
Nagios XiApplication · Nagios

CVE-2022-50586

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.8.9 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.9 are vulnerable to cross-site scripting (XSS) in the BPI component via the info URL field. 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 versions prior to 5.8.9 contain a stored XSS vulnerability in the BPI (Business Process Intelligence) component. The info URL field accepts user-supplied input without proper validation or escaping, allowing an attacker to inject malicious JavaScript that executes in victims' browsers.

MitigationUpgrade to Nagios XI version 5.8.9 or later which includes proper input validation and output escaping for the BPI component's info URL field.

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

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 installation and version
    Check the installed Nagios XI version using the web interface (typically at /nagiosxi/about.php) or by running: rpm -q nagiosxi or cat /usr/local/nagiosxi/etc/version.ini
    Affected if Version is prior to 5.8.9 (versions 5.8.0 through 5.8.8 are affected)
  2. Confirm BPI component is in use
    Navigate to the BPI (Business Process Intelligence) component in the Nagios XI web interface, typically found under the 'Configure' menu or at /nagiosxi/index.php?pi=ba
    Affected if The BPI component is accessible and configured in the environment
  3. Examine BPI info URL field for suspicious content
    In the BPI component interface, review any BPI groups that have an 'Info URL' field configured. Check for any unexpected or encoded JavaScript patterns (such as <script>, javascript:, onerror=, onload=, or hex/URL encoded payloads)
    Affected if The info URL field contains unsanitized user-supplied JavaScript or HTML content
  4. Review HTTP request logs for BPI info URL submissions
    Examine web server access logs (typically in /var/log/httpd/ or /var/log/nginx/) for POST requests to BPI configuration endpoints that contain suspicious patterns in the info_url parameter
    Affected if Recent requests contain malicious payloads in info_url parameters

You are affected if running Nagios XI version below 5.8.9 AND the BPI component is in use with an info URL field containing or having contained unsanitized input.

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.9 or later
Fixed in 5.8.9
Interim mitigation

Upgrade to Nagios XI version 5.8.9 or later which includes proper input validation and output escaping for the BPI component's info URL field.

Recommended fix High confidence

Nagios XI 5.8.9 or later

  1. 1. Back up the Nagios XI database and configuration files before proceeding with any upgrade.
  2. 2. Log into the Nagios XI web interface as an administrative user.
  3. 3. Navigate to the Admin > System Information section to confirm the current installed version.
  4. 4. Run the Nagios XI update script or use the web-based update mechanism to upgrade to version 5.8.9 or later: sudo /usr/local/nagiosxi/scripts/upgrade_to_latest.sh
  5. 5. After the upgrade completes, clear browser cache and cookies.
  6. 6. Log back into Nagios XI and navigate to the BPI component.
  7. 7. Verify that the info URL field now properly sanitizes input and the vulnerability is resolved by attempting a benign XSS test (without actually exploiting).
  8. 8. Confirm the upgraded version in Admin > System Information shows 5.8.9 or higher.

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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