CriticalCVE-2021-25296

    Nagios XI OS Command Injection (CVE-2021-25296)

    Published Last modified In CISA KEV since Sources: CVE.org

    Share

    What is affected, what to do

    This vulnerability allows OS command injection on the Nagios XI server, enabling an authenticated attacker to execute arbitrary commands via a single HTTP request. It is actively exploited, as evidenced by its inclusion in the CISA KEV catalog. Affected products include Nagios XI versions 5.5.6 to 5.7.5. Immediate patching to the latest version is critical to mitigate this risk.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Nagios XI lte 5.5.6..5.7.5

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    71.9 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.44

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    223.11 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    71.9 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.44
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 4 February 2025

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable and needs no user interaction. It requires only a low-privileged account and yields full command execution on the monitoring server. It sits among the CVEs most likely to be exploited, with public exploit code available for a long time and frequently chained with sibling Nagios XI wizard injections. Nagios XI is a high-value pivot: it has network reach into almost every monitored system and stores privileged credentials such as WMI domain accounts and SSH keys. That makes it ideal for lateral movement even though CISA does not flag ransomware use. Treat any remaining instance on 5.7.5 or earlier as high priority, and as critical with a 24-hour patch target if it is reachable from the internet or from user networks.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory and upgrade: Every Nagios XI instance on versions 5.5.6 through 5.7.5 is affected. Upgrade to a release later than 5.7.5. A patch is available from the vendor; look up the exact fixed version in the Nagios security advisory. Check the current version via Admin > System Information or /usr/local/nagiosxi/var/xiversion.
      • Restrict web UI exposure: Until patched, limit access to the Nagios XI web UI (TCP 80/443) to a dedicated admin network or jump host. Remove any internet exposure immediately.
      • Clean up user accounts: Exploitation only requires a low-privileged authenticated account. Disable unused accounts and reset default or weak passwords. Revoke monitoring-wizard and object-configuration rights from non-admin users.
      • Hunt for compromise: Grep web server logs for monitoringwizard.php requests with wizard=windowswmi from unexpected users or source IPs. On any hit, isolate the host and preserve evidence.
      • Rotate stored credentials: Nagios XI stores WMI accounts (often domain accounts), SSH keys, SNMP communities and API keys for monitored systems. If exploitation is suspected, rotate these first, along with the Nagios XI API token.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the Nagios XI server in a dedicated management VLAN. Allow egress only to the monitoring ports it actually needs, such as WMI/RPC, SSH, SNMP and NRPE (TCP 5666). Block outbound internet HTTP/HTTPS to hinder payload staging and reverse shells.
      • WAF/reverse proxy: Inspect requests to /nagiosxi/config/monitoringwizard.php with wizard=windowswmi for shell metacharacters in parameter values (;, |, `, $(, &&, %0a) and drop them. Alternatively, deny the path to everyone except whitelisted admin IPs.
      • Configuration change: If the Windows WMI wizard isn't needed, uninstall it via Admin > Manage Config Wizards. This removes the vulnerable windowswmi.inc.php.
      • Endpoint hardening: Run SELinux in enforcing mode. Mount /tmp and /dev/shm with noexec to limit what the apache user can execute. Minimise sudo rules for nagios/apache, since they are a well-known root escalation path on Nagios XI.
      • IAM: Front the web UI with central authentication (LDAP/AD) plus MFA via a reverse proxy. Run WMI monitoring accounts with least privilege rather than as domain admins.
    3. Runbook step 3

      Detection rules

      • Web access logs: Look for GET|POST /nagiosxi/config/monitoringwizard.php containing wizard=windowswmi and URL-encoded metacharacters (%3B, %7C, %60, %24%28). Example SPL: index=web uri_path="*monitoringwizard.php" uri_query="*windowswmi*" (uri_query="*%3B*" OR uri_query="*%7C*" OR uri_query="*%60*")
      • EDR/Sysmon for Linux (EID 1) process ancestry: Watch for httpd or php-fpm spawning sh/bash, which in turn launches curl, wget, nc, python*, perl, base64 or chmod. Sigma shape: ParentImage|endswith: '/httpd' AND Image|endswith: ['/curl','/wget','/nc','/python3'].
      • auditd: Add -a always,exit -F arch=b64 -S execve -F uid=apache -k web_exec. Then alert on type=EXECVE with uid=apache running anything other than known plugins under /usr/local/nagios/libexec.
      • Network telemetry (Zeek/Suricata): Flag new outbound connections from the Nagios XI server to internet destinations and long-lived TCP sessions on unusual ports (reverse shells). In Zeek conn.log, filter for id.orig_h == <nagiosxi> with a responder outside RFC1918 space.
      • File integrity: Alert on new or modified files under /usr/local/nagiosxi/html/, /tmp or /var/www (webshells). Do the same for changes to /etc/sudoers.d/ and to crontabs of apache and nagios.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Nagios XI version xi-5.7.5 is affected by OS command injection. The vulnerability exists in the file /usr/local/nagiosxi/html/includes/configwizards/windowswmi/windowswmi.inc.php due to improper sanitization of authenticated user-controlled input by a single HTTP request, which can lead to OS command injection on the Nagios XI server.

    Source: CISA KEV Catalog, NVD (NIST), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    nagiosnagios_xi
    • 5.5.6 – ≤ 5.7.5
    • —

    Vendors and products

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Packet StormNagios XI 5.7.5 Remote Code Execution (opens in a new tab)packetstormsecurity.comPoC (publicly reported)reported, not verified—
    Packet StormNagios XI 5.7.5 Remote Code Execution (opens in a new tab)packetstormsecurity.comPoC (publicly reported)reported, not verified—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. NVD analysis modifiedNVD

    2. NVD analysis modifiedNVD

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Reference typechanged
      MITRE: https://assets.nagios.com/downloads/nagiosxi/versions.php Types: Exploit, Product
      MITRE: https://assets.nagios.com/downloads/nagiosxi/versions.php Types: Product
      Reference typechanged
      CVE: https://assets.nagios.com/downloads/nagiosxi/versions.php Types: Exploit, Product
      CVE: https://assets.nagios.com/downloads/nagiosxi/versions.php Types: Product

      Source identifier: nvd@nist.gov

    3. Record modifiedMITRE

      2 individual changes: Reference, Reference type

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceremoved
      http://nagios.com
      —
      Reference typeremoved
      http://nagios.com Types: Product
      —

      Source identifier: cve@mitre.org

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2021-25296
    <a href="https://intel.neosec.eu/en/cve/CVE-2021-25296"><img src="https://intel.neosec.eu/badge/cve/CVE-2021-25296.svg?lang=en" alt="CVE-2021-25296 – NEOSEC Intel" height="20"></a>