dbcve.org
Nagios XiApplication · Nagios

CVE-2024-54957

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-27
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 vulnerable to an open redirect flaw on the Tools page, exploitable by users with read-only permissions. This vulnerability allows an attacker to craft a malicious link that redirects users to an arbitrary external URL without their consent.

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 2024R1.2.2 contains an open redirect vulnerability in the Tools page. Users with read-only permissions can craft malicious URLs containing a redirect parameter that forces the application to redirect victims to attacker-controlled external websites, enabling phishing attacks.

MitigationImplement strict validation of redirect URLs on the Tools page, ensuring only relative/internal paths are allowed or use an explicit allowlist of permitted domains. Consider adding a warning banner when redirecting to external sites.

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 and version
    Check the installed Nagios XI version. This is typically visible in the XI interface footer, or via command line using 'cat /usr/local/nagiosxi/html/includes/version.php' or checking system package information.
    Affected if The installed version is Nagios XI 2024 (specifically 2024R1.2.2 or close to it)
  2. Verify Tools page is accessible
    Log into Nagios XI with a read-only user account and navigate to the Tools page. The URL typically contains '/nagiosxi/tools/' or similar path.
    Affected if The Tools page loads and is accessible to read-only users
  3. Check for redirect parameter behavior
    Examine the Tools page URL for any redirect-related parameters (commonly 'redirect', 'url', 'target', or similar). Test by appending a known external domain to the parameter (e.g., ?redirect=http://example.com) and observe if the application redirects.
    Affected if The application accepts an external URL in a redirect parameter and performs the redirect without validation or warning
  4. Review web server logs for redirect patterns
    Check web server access logs (typically in /var/log/httpd/ or /var/log/nginx/) for requests to the Tools page with external domains in query parameters.
    Affected if Logs show requests containing external URLs being passed to Tools page parameters

A user is affected if running Nagios XI 2024R1.2.2 with the Tools page accessible and a redirect parameter that allows unvalidated external URLs to trigger redirection.

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

Implement strict validation of redirect URLs on the Tools page, ensuring only relative/internal paths are allowed or use an explicit allowlist of permitted domains. Consider adding a warning banner when redirecting to external sites.

Recommended fix Moderate confidence

Latest stable Nagios XI 2024 release (post-2024R1.2.2)

  1. 1. Identify your current Nagios XI version by navigating to the Admin > System Information page in the web interface
  2. 2. Confirm the version is 2024R1.2.2 or another affected 2024 release
  3. 3. Back up your Nagios XI configuration and database before performing any upgrade
  4. 4. Download the latest stable Nagios XI release from the official Nagios website (www.nagios.com) or Nagios XI customer portal
  5. 5. Apply the upgrade following the official Nagios XI upgrade documentation
  6. 6. After upgrade, verify the Tools page no longer contains vulnerable redirect parameters
  7. 7. Confirm the upgrade was successful by checking the version in Admin > System Information
Caveat Standard Nagios XI upgrade considerations apply - review release notes for breaking changes between versions

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 help mitigating

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-2024-54957 — 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-54957 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