dbcve.org
Nagios XiApplication · Nagios

CVE-2024-13992

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-31
Fix available
A fix is available. Upgrade to 2024 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 < 2024R1.1 is vulnerable to a cross-site scripting (XSS) when a user visits the "missing page" (404) page after following a link from another website. The vulnerable component, page-missing.php, fails to properly validate or escape user-supplied input, allowing an attacker to craft a malicious link that, when visited by a victim, executes arbitrary JavaScript in the victim’s browser within the Nagios XI domain.

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 2024R1.1 contain a reflected XSS vulnerability in page-missing.php (the 404 error page). The component fails to properly validate or escape user-supplied input (the missing URL), allowing an attacker to inject malicious JavaScript that executes in victim's browser when they visit a crafted link.

MitigationUpgrade to Nagios XI 2024R1.1 or later. Alternatively, implement proper input validation and output encoding on the page-missing.php file to sanitize user-supplied input before rendering.

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= 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
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. Identify Nagios XI version
    Check the installed Nagios XI version by examining /usr/local/nagiosxi/etc/xi-version.txt or the version file in the web interface
    Affected if Version is 2024 or earlier (prior to 2024R1.1)
  2. Locate page-missing.php
    Verify the presence of page-missing.php in the Nagios XI web root directory (typically /usr/local/nagiosxi/html/page-missing.php)
    Affected if The file exists on the system and the version is in the affected range
  3. Examine input handling in page-missing.php
    Inspect the source code of page-missing.php and look for where the missing URL parameter is output, checking if it is properly sanitized or if raw user input is reflected back
    Affected if The file reflects the URL parameter without proper validation or output encoding

The system is affected if Nagios XI version is 2024 or earlier AND page-missing.php exists and fails to sanitize the user-supplied URL before rendering it in the page

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 2024 or later
Fixed in 2024
Interim mitigation

Upgrade to Nagios XI 2024R1.1 or later. Alternatively, implement proper input validation and output encoding on the page-missing.php file to sanitize user-supplied input before rendering.

Recommended fix High confidence

Nagios XI 2024R1.1 or later

  1. 1. Back up the entire Nagios XI system, including the database and configuration files, before performing any upgrade
  2. 2. Download Nagios XI version 2024R1.1 or later from the official Nagios download portal at www.nagios.com
  3. 3. Run the Nagios XI upgrade script or use the web-based upgrade interface, following the official upgrade instructions
  4. 4. After upgrade completion, verify the version number reflects the new release (2024R1.1 or later)
  5. 5. Test the page-missing.php endpoint by accessing a non-existent page with a test parameter (e.g., ?test=<script>alert(1)</script>) to confirm XSS is mitigated
Caveat Point releases typically have minimal breaking changes; review Nagios XI release notes for any known compatibility issues 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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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