dbcve.org
Nagios XiApplication · Nagios

CVE-2022-50584

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.8.8 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
The Core Config Manager (CCM) in Nagios XI versions prior to CCM 3.1.6 / Nagios XI 5.8.8 contains a cross-site scripting (XSS) vulnerability via the search and deletion interfaces. 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

The Core Config Manager (CCM) in Nagios XI versions prior to 5.8.8 contains a reflected cross-site scripting (XSS) vulnerability. The search and deletion interfaces fail to properly validate or escape user-supplied input, allowing attackers to inject arbitrary JavaScript that executes in the context of a victim's browser.

MitigationUpgrade to Nagios XI 5.8.8 / CCM 3.1.6 or later, which includes proper input validation and output encoding to prevent XSS attacks.

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

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. Verify Nagios XI is installed
    Access the web interface or check for Nagios XI directories (typically /usr/local/nagiosxi/) on the target system
    Affected if The system is running Nagios XI
  2. Determine the installed Nagios XI version
    Check the version information in the web interface (usually in the footer or under 'About' in the admin menu) or inspect version files in the Nagios XI installation directory
    Affected if The version number is lower than 5.8.8
  3. Confirm the Core Config Manager (CCM) module is accessible
    Log into the Nagios XI web interface and navigate to the Core Config Manager (CCM) section, typically found under 'Config' in the main menu
    Affected if CCM is accessible and enabled for the user account
  4. Check if CCM version can be identified
    Look for CCM version information within the Core Config Manager interface or in CCM-related configuration files
    Affected if CCM version is below 3.1.6 (if version info is displayed)

A user is affected if they are running any version of Nagios XI prior to 5.8.8 with the Core Config Manager module accessible.

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.8 or later
Fixed in 5.8.8
Interim mitigation

Upgrade to Nagios XI 5.8.8 / CCM 3.1.6 or later, which includes proper input validation and output encoding to prevent XSS attacks.

Recommended fix High confidence

Nagios XI 5.8.8 (or latest stable release)

  1. Verify current Nagios XI version by navigating to Admin > System Information in the web interface
  2. Back up the Nagios XI database and configuration files before upgrading
  3. Back up the entire /usr/local/nagiosxi directory if possible
  4. Run the Nagios XI auto-update process or download the latest version from the Nagios website
  5. Apply the upgrade following Nagios official upgrade documentation for version 5.8.8
  6. After upgrade, verify the CCM version shows 3.1.6 or later
  7. Test the Core Config Manager search and deletion interfaces to confirm the XSS vulnerability is patched
Caveat Ensure compatibility with existing plugins and configurations; review release notes for any migration requirements

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-2022-50584 — 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-50584 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