dbcve.org
Nagios XiApplication · Nagios

CVE-2024-14002

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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.4 contain a local file inclusion (LFI) vulnerability via its NagVis integration. An authenticated user can supply crafted path values that cause the server to include local files, potentially exposing sensitive information from the underlying host.

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.4 contain a local file inclusion (LFI) vulnerability in the NagVis integration component. An authenticated attacker can supply crafted path values to include and read local files from the server, potentially exposing sensitive system information.

MitigationUpgrade Nagios XI to version 2024R1.1.4 or later to patch the LFI vulnerability in the NagVis integration.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installation
    Locate Nagios XI by checking for the presence of /usr/local/nagiosxi/ or /opt/nagiosxi/ directories, or by running 'ls -la /usr/local/nagios/' and checking for XI-specific files
    Affected if Nagios XI is installed on the system
  2. Determine installed Nagios XI version
    Check the version file typically located at /usr/local/nagiosxi/etc/versions.ini or run the command: cat /usr/local/nagiosxi/etc/versions.ini | grep -i 'nagios xi'
    Affected if The version is below 2024R1.1.4 (including any 2024.x.x version) or cannot be determined to be 2024R1.1.4 or later
  3. Verify NagVis component is accessible
    Check if NagVis is installed by looking for /usr/local/nagiosxi/html/includes/nagvis/ or /opt/nagiosxi/html/includes/nagvis/ directories, or attempt to access the NagVis UI endpoint (typically /nagiosxi/nagvis/)
    Affected if NagVis component is present and accessible via the web interface
  4. Review web server access logs for LFI indicators
    Examine web server access logs (typically in /usr/local/nagiosxi/var/logs/ or /var/log/httpd/) for suspicious requests containing path traversal patterns such as '../', '..\', or includes of system files like /etc/passwd within NagVis-related URLs
    Affected if Suspicious LFI path traversal requests are found in logs targeting NagVis endpoints

A user is affected if Nagios XI is installed with a version prior to 2024R1.1.4 AND the NagVis component is enabled and accessible, regardless of authentication status in the log evidence.

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 Nagios XI to version 2024R1.1.4 or later to patch the LFI vulnerability in the NagVis integration.

Recommended fix Moderate confidence

2024R1.1.4

  1. 1. Identify the current Nagios XI version by navigating to the Admin > System Information section in the web UI.
  2. 2. If the current version is prior to 2024R1.1.4, plan for an upgrade to the 2024R1.1.4 release or later.
  3. 3. Before upgrading, ensure a complete backup of the Nagios XI system including the database and configuration files.
  4. 4. Follow the standard Nagios XI upgrade procedure documented in the official administration guide.
  5. 5. After upgrading, verify the NagVis integration functionality works correctly.
  6. 6. Confirm the version has been updated to 2024R1.1.4 or newer in the Admin > System Information section.
Caveat Standard Nagios XI upgrade risks 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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