dbcve.org
Nagios XiApplication · Nagios

CVE-2024-14001

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
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.3 are vulnerable to cross-site scripting (XSS) via the Executive Summary Report component. 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

Nagios XI versions prior to 2024R1.1.3 contain a stored XSS vulnerability in the Executive Summary Report component. Attackers can inject malicious JavaScript through insufficiently validated user-supplied input, which then executes in the context of other users' browsers when they view the report.

MitigationUpgrade to Nagios XI 2024R1.1.3 or later to obtain the patch for this vulnerability.

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. Confirm Nagios XI installation and locate version file
    Look for the file /usr/local/nagiosxi/html/includes/version.inc or check the Nagios XI web interface footer for the version number
    Affected if The displayed version is earlier than 2024R1.1.3 or shows exactly 2024 (any point release)
  2. Identify if Executive Summary Report is accessible
    Navigate to the Reports section in the Nagios XI web interface and locate the Executive Summary Report component, or query the backend database for reports configuration
    Affected if The component exists and is accessible to users who can create or view reports
  3. Check for suspicious stored XSS payloads in report data
    Examine the database tables (such as nagiosql or report-related tables) for unusual JavaScript tags, event handlers, or encoded payloads in fields that populate the Executive Summary Report
    Affected if Any record contains script tags, img onerror, body onload, or similar XSS vectors in user-controllable report fields
  4. Review web server access logs for XSS attack patterns
    Search web server access logs (typically in /var/log/httpd/ or /var/log/nginx/) for requests to /nagiosxi/reports/executive_summary containing suspicious patterns like <script, javascript:, onerror=, onload=
    Affected if Logs show requests with XSS payloads directed at the Executive Summary Report endpoint

A user is affected if their Nagios XI version is 2024 (any subversion) or any version prior to 2024R1.1.3 and the Executive Summary Report feature is in use.

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.3 or later to obtain the patch for this vulnerability.

Recommended fix Moderate confidence

2024R1.1.3 or later

  1. Download the latest Nagios XI version from the official Nagios website (www.nagios.com)
  2. Ensure you have a complete backup of your current Nagios XI installation and database
  3. Review the official Nagios XI upgrade documentation for your current version
  4. Execute the upgrade process following Nagios best practices for production systems
  5. After upgrade, verify the Executive Summary Report component is functioning correctly
  6. Clear browser cache and test that the XSS vulnerability is no longer present in the Executive Summary Report
Caveat Standard Nagios XI upgrade considerations apply; test in non-production environment first

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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