dbcve.org
Nagios XiApplication · Nagios

CVE-2022-50587

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) via the Apply Configuration error text. 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 cross-site scripting (XSS) vulnerability in the Apply Configuration error text field. The application fails to properly validate or escape user-supplied input, allowing an attacker to inject malicious JavaScript that executes in the context of a victim's browser when the error text is displayed.

MitigationUpgrade to Nagios XI version 5.8.9 or later to obtain the security patch that addresses this XSS vulnerability.

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. Determine installed Nagios XI version
    Log into the Nagios XI web interface and navigate to Admin > System Information, or run 'cat /usr/local/nagiosxi/var/version.txt' from the command line to identify the exact version number
    Affected if The installed version is lower than 5.8.9 (for example, 5.8.0 through 5.8.8)
  2. Locate the Apply Configuration feature
    In the Nagios XI web interface, navigate to the Configure > Apply Configuration menu path, or look for the configuration deployment workflow section
    Affected if The Apply Configuration feature is present and accessible in the installed version
  3. Identify the error text field
    Access the Apply Configuration section and locate any error message or error text input/display area where configuration deployment feedback is shown
    Affected if The error text field exists and accepts user-supplied input without visible sanitization
  4. Inspect stored error text content
    Check the backend database or configuration files where Apply Configuration error messages are stored, typically in the Nagios XI MySQL database under tables related to configuration deployment or in /usr/local/nagiosxi/var/ logs
    Affected if The stored error text field contains unsanitized or potentially malicious content

The environment is affected if the installed Nagios XI version is below 5.8.9 and the Apply Configuration error text field can display or store unsanitized user 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 to obtain the security patch that addresses this XSS vulnerability.

Recommended fix Moderate confidence

5.8.9

  1. 1. Back up your current Nagios XI installation, including the database and configuration files
  2. 2. Download Nagios XI version 5.8.9 from the official Nagios website (www.nagios.com)
  3. 3. Run the Nagios XI upgrade script or follow the official upgrade documentation for your specific operating system
  4. 4. Verify the upgrade was successful by logging into the Nagios XI web interface
  5. 5. Test the Apply Configuration functionality to confirm the vulnerability is remediated
Caveat Review Nagios XI 5.8.9 release notes for any changes to features or configuration compatibility 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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