dbcve.org
Nagios XiApplication · Nagios

CVE-2024-54958

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 2024R1.2.2 is susceptible to a stored Cross-Site Scripting (XSS) vulnerability in the Tools page. This flaw allows an attacker to inject malicious scripts into the Tools interface, which are then stored and executed in the context of other users accessing the page.

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

Nagios XI 2024R1.2.2 contains a stored Cross-Site Scripting (XSS) vulnerability in the Tools page. An authenticated attacker can inject malicious JavaScript payloads into the Tools interface, which are persisted and executed when other users view or interact with the Tools page, allowing session hijacking, credential theft, or further malicious actions.

MitigationApply the vendor patch when released; until then, disable or restrict access to the Tools page for untrusted users, and implement output encoding and input validation on all user-supplied data in the affected component.

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:= 2024

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Nagios XI installation
    Locate Nagios XI by checking for the Nagios XI web interface or looking for /usr/local/nagiosxi or similar installation directories. Use 'rpm -qa | grep nagios' or 'dpkg -l | grep nagios' on Linux systems.
    Affected if Nagios XI is installed on the system
  2. Identify installed Nagios XI version
    Access the Nagios XI admin interface and navigate to Admin > System Information, or check the version file at /usr/local/nagiosxi/var/xi-sys.cfg, or run: cat /usr/local/nagiosxi/var/version.txt
    Affected if The installed version is 2024R1.2.2 or any 2024 release (version equals 2024)
  3. Verify access to Tools page
    Log into Nagios XI as a standard user and navigate to Tools in the main menu to confirm the page is accessible. Check user permissions under Admin > Users to see if the authenticated user has Tools page access.
    Affected if The authenticated user has access to the Tools page functionality
  4. Inspect Tools page for stored XSS payloads
    View the source HTML of the Tools page in your browser (right-click > View Page Source) or use browser developer tools to examine the page content. Look for any script tags, event handlers, or suspicious JavaScript in the page body that may have been injected into Tools page fields.
    Affected if Unexpected script tags, javascript: URIs, or encoded payloads appear in the Tools page HTML

You are affected if Nagios XI version 2024 is installed and the Tools page is accessible to authenticated users, as the stored XSS vulnerability exists in that component.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when released; until then, disable or restrict access to the Tools page for untrusted users, and implement output encoding and input validation on all user-supplied data in the affected component.

Recommended fix Moderate confidence

Nagios XI 2024R1.2.3 or later stable release

  1. 1. Back up your current Nagios XI installation and database before proceeding
  2. 2. Identify your current Nagios XI version by navigating to Admin > System Information in the web interface
  3. 3. Download the latest stable Nagios XI 2024 release from the official Nagios download portal (support.nagios.com)
  4. 4. Apply the upgrade following Nagios XI standard upgrade procedures: run the upgrade script or use the web-based upgrade interface
  5. 5. After upgrade, verify the Tools page functionality and confirm the XSS payload is no longer executable
  6. 6. Clear browser cache and test with a non-malicious script to confirm the fix
Caveat Standard Nagios XI upgrade risks apply - test in staging first; ensure backups are verified; some custom configurations may need reapplication after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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