dbcve.org
Nagios XiApplication · Nagios

CVE-2022-50585

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
The Core Config Manager (CCM) in Nagios XI versions prior to CCM 3.1.7 / Nagios XI 5.8.9 contains a cross-site scripting (XSS) vulnerability via the Audit Log page search input. 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

The Core Config Manager (CCM) in Nagios XI contains a stored cross-site scripting (XSS) vulnerability in the Audit Log page search input field. User-supplied input to this field is not properly validated or escaped, allowing an attacker to inject malicious JavaScript that executes in the context of a victim's browser session.

MitigationUpgrade to Nagios XI 5.8.9 / CCM 3.1.7 or later which contains the patched version of the Core Config Manager that properly sanitizes user input in the Audit Log search functionality.

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. Check installed Nagios XI version
    Log into the Nagios XI web interface and navigate to Help > About, or run 'cat /usr/local/nagiosxi/etc/components/version.ini' from the server command line
    Affected if The displayed version is earlier than 5.8.9
  2. Check Core Config Manager (CCM) version
    Access the CCM interface via the Nagios XI menu (Configure > Core Config Manager) and locate the version information, typically found in the CCM footer or system information page
    Affected if The CCM version is earlier than 3.1.7 or the version cannot be determined (indicating an older build)
  3. Confirm CCM Audit Log functionality is present
    In the CCM interface, navigate to the Audit Log page (typically under System > Audit Log or similar) and verify the search input field exists
    Affected if The Audit Log search field is present and accessible to the user
  4. Determine if CCM is enabled and accessible
    Verify that the Core Config Manager component is installed and accessible in the Nagios XI environment by checking if the CCM menu item appears in the Nagios XI navigation
    Affected if CCM is installed and the Audit Log feature is accessible to authenticated users

You are affected if your Nagios XI version is below 5.8.9 (or CCM version below 3.1.7) AND the Core Config Manager with Audit Log functionality is enabled and accessible in your environment.

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 5.8.9 / CCM 3.1.7 or later which contains the patched version of the Core Config Manager that properly sanitizes user input in the Audit Log search functionality.

Recommended fix High confidence

Nagios XI 5.8.9 (or later) / CCM 3.1.7

  1. Confirm current Nagios XI version by navigating to Admin > System Information in the web interface
  2. Create a complete backup of the Nagios XI system including the database and configuration files
  3. Access the Nagios XI administration interface and navigate to the Updates section or use the built-in update mechanism
  4. Upgrade to Nagios XI 5.8.9 or later (which includes CCM 3.1.7)
  5. After upgrade completion, verify the version by checking Admin > System Information
  6. Clear browser cache and test the Audit Log page to confirm the XSS vulnerability is resolved by entering test script tags in the search input

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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