dbcve.org
Nagios XiApplication · Nagios

CVE-2024-14005

HIGH · 8.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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.2 contain a command injection vulnerability in the Docker Wizard. Insufficient validation of user-supplied input in the wizard allows an authenticated administrator to inject shell metacharacters that are incorporated into backend command invocations. Successful exploitation enables arbitrary command execution with the privileges of the Nagios XI web application user.

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.2 contain a command injection vulnerability in the Docker Wizard component. The vulnerability stems from insufficient validation of user-supplied input, allowing an authenticated administrator to inject shell metacharacters that get incorporated into backend command invocations. Successful exploitation enables arbitrary command execution with the privileges of the Nagios XI web application user.

MitigationUpgrade Nagios XI to version 2024R1.2 or later to patch the vulnerability. If immediate upgrade is not feasible, disable the Docker Wizard and review system logs for signs of exploitation.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 and version
    Navigate to the Nagios XI web interface, typically at /nagiosxi or check the footer of any page for the version number. Alternatively, run 'rpm -q nagiosxi' or 'dpkg -l nagios-xi' on the server to get the installed version.
    Affected if The installed version is prior to 2024R1.2 or matches version 2024.
  2. Verify Docker Wizard is accessible
    Log into Nagios XI as an administrator and attempt to access the Docker Wizard component. This is typically found under 'Configure' > 'Wizard' > 'Docker' or by navigating to /nagiosxi/includes/components/wizard/ in the URL.
    Affected if The Docker Wizard interface loads successfully, indicating the component is enabled and accessible.
  3. Review Nagios XI logs for suspicious activity
    Check the following log files for signs of command injection attempts: /usr/local/nagiosxi/var/nagios.log, /var/log/httpd/error_log (or /var/log/apache2/error.log), and /usr/local/nagiosxi/logs/xi-sys.log. Search for entries containing shell metacharacters like ';', '|', '$(', '`', or unexpected commands.
    Affected if Log entries show suspicious commands containing shell metacharacters or unexpected command executions, particularly those associated with Docker operations.
  4. Check for unauthorized cron jobs or scheduled tasks
    Run 'crontab -l' as the nagios user and check /etc/cron.d/ for any unexpected cron entries that may have been created through exploitation.
    Affected if New or unexpected cron jobs exist that were not intentionally created by administrators.

A user is affected if their Nagios XI installation is version 2024 or any version prior to 2024R1.2 AND the Docker Wizard component is enabled and accessible.

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.2 or later to patch the vulnerability. If immediate upgrade is not feasible, disable the Docker Wizard and review system logs for signs of exploitation.

Recommended fix High confidence

Nagios XI 2024R1.2

  1. Back up the Nagios XI system and database before proceeding with any upgrade
  2. Download Nagios XI version 2024R1.2 from the official Nagios website (www.nagios.com)
  3. Apply the upgrade to the Nagios XI installation following the standard upgrade procedure
  4. After upgrade, verify the Docker Wizard component is functioning correctly
  5. Confirm the system is running version 2024R1.2 by checking the Nagios XI administration interface

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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