dbcve.org
Nagios XiApplication · Nagios

CVE-2018-25122

HIGH · 8.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.4.13 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 5.4.13 contain a remote code execution vulnerability in the Component Download page. The download/import handler used unsafe command construction with attacker-controlled input and lacked sufficient validation and output encoding, allowing an authenticated user to inject commands or otherwise execute arbitrary code with the privileges of the application service.

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

Authenticated command injection vulnerability in Nagios XI's Component Download page allows attackers to inject arbitrary commands through unsafe construction in the download/import handler, which lacks proper input validation and output encoding, enabling remote code execution with application service privileges.

MitigationUpgrade to Nagios XI version 5.4.13 or later to obtain the vendor patch; if immediate upgrade is not feasible, restrict access to the Component Download functionality to trusted users only.

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:< 5.4.13

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
    Check the Nagios XI version by navigating to the admin interface or running: cat /usr/local/nagiosxi/etc/components/version.ini or checking the Nagios XI about page in the web GUI
    Affected if The installed version is found to be below 5.4.13 (e.g., 5.4.12, 5.4.10, 5.3.x, etc.)
  2. Locate the Component Download handler
    Inspect the file system for the component download/import handler. Typical path: /usr/local/nagiosxi/html/includes/components/downloadhandler.php or similar PHP handler in the includes/components/ directory
    Affected if The file exists and the installed Nagios XI version is below 5.4.13
  3. Check Component Download feature accessibility
    Log into Nagios XI as a user with access to Admin > System Extensions > Component Downloads (or similar path under the Components or Extends section)
    Affected if The Component Download page is accessible and the Nagios XI version is below 5.4.13
  4. Verify handler file integrity
    Compare the suspected vulnerable handler file with known-good versions or examine the source code for unsafe use of system/exec/passthru functions with unsanitized user input
    Affected if The handler uses shell_exec, exec, or similar functions without proper input sanitization on the download/import parameters and the version is below 5.4.13

A system is affected if Nagios XI is installed with a version lower than 5.4.13 and the Component Download functionality is accessible to the attacker.

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

Upgrade to Nagios XI version 5.4.13 or later to obtain the vendor patch; if immediate upgrade is not feasible, restrict access to the Component Download functionality to trusted users only.

Recommended fix High confidence

Nagios XI 5.4.13 or later

  1. Back up the Nagios XI system and database before starting the upgrade process
  2. Download Nagios XI version 5.4.13 or later from the official Nagios website (www.nagios.com)
  3. Run the official Nagios XI upgrade script or follow the documented upgrade procedure
  4. After upgrade, verify the Component Download functionality works correctly
  5. Confirm the upgrade was successful by checking the Nagios XI version in the web interface

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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