CriticalCVE-2019-15949

    Nagios XI Remote Code Execution Vulnerability (CVE-2019-15949)

    Published In CISA KEV since Sources: CVE.org

    Share

    What is affected, what to do

    Nagios XI before 5.6.6 allows remote command execution as root. The exploit requires access to the server as the nagios user, or access as the admin user via the web interface.

    The vulnerability is being actively exploited; treat it as a priority. Update Nagios XI to version 5.6.6. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Nagios XI lt *..5.6.6
    Fixed in
    • Nagios XI 5.6.6

    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

    77.0 %

    EPSS score

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

    Source: FIRST EPSS, percentile 99.56

    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.30 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
    77.0 %
    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.56
    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
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-78

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw chains an authenticated web-UI feature with a passwordless sudo rule to give reliable root code execution. A public Metasploit module exists, and the CVE ranks among those most likely to be exploited. Attackers typically pair it with weak or leaked admin credentials or other Nagios XI authentication weaknesses. They target the monitoring server because it concentrates credentials and network reach across the estate. Low privileges are required and no ransomware use is flagged, but any unpatched instance with a reachable UI or several admin accounts should still be treated as critical and upgraded within 72 hours. This applies even more in KRITIS environments, where the monitoring host often bridges into OT-adjacent segments.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Upgrade Nagios XI to 5.6.6 or later, since every release before 5.6.6 is vulnerable. Check the running version via Admin → Check for Updates or /usr/local/nagiosxi/var/xiversion. Prefer the current supported release, because later versions closed further sudo and privilege-escalation paths.
      • Until patched, restrict the web UI (/nagiosxi/, ports 80/443) to an admin jump-host network or VPN. Nagios XI must never be internet-facing.
      • Enumerate all Nagios XI accounts with the admin role or plugin-management rights. Disable unused accounts and rotate passwords and API keys for the rest, because exploitation starts from an authenticated session.
      • Verify the integrity of check_plugin in the plugin directory (typically /usr/local/nagios/libexec/). Compare its hash, mtime and content against a known-good copy. Embedded shell commands, reverse-shell one-liners or curl/wget calls indicate compromise.
      • If you find signs of exploitation, isolate the host and preserve evidence: memory, /var/log/httpd, /var/log/secure, and the nagios and root shell history. Treat the box as root-compromised. Rotate every credential stored on it for monitored systems, including SNMP communities, SSH keys, NRPE secrets and WMI/domain service accounts.
    2. Runbook step 2

      Mitigation layers

      • Configuration / sudo: Review the sudo rules for nagios (sudo -l -U nagios, typically /etc/sudoers.d/nagiosxi). Temporarily comment out the passwordless entry for getprofile.sh if system-profile downloads aren't operationally required.
      • Filesystem hardening: As a stopgap, set check_plugin to root:root with mode 0755 and lock it with chattr +i. Test the interaction with the upgrade process first.
      • IAM / least privilege: Limit plugin-management rights and access to Admin → Manage Plugins to a few named administrators. Put MFA or SSO in front of the web UI, for example via an authenticating reverse proxy.
      • Network segmentation: Keep Nagios XI in a management VLAN. Allow egress only to monitored targets and update servers, and block and log outbound connections to unusual ports (reverse shells) at the perimeter.
      • WAF / reverse proxy: Allow requests to profile.php?cmd=download and plugin uploads (monitoringplugins.php POST uploads) only from the admin source range, and deny everything else.
    3. Runbook step 3

      Detection rules

      • Web access logs: The canonical exploit chain is a POST upload of a plugin named check_plugin, followed within minutes by GET .../profile/profile.php?cmd=download from the same source IP. SPL example: index=web uri_path="*profile.php" uri_query="*cmd=download*" | stats count by src_ip, user
      • auditd: Watch for writes to the plugin with -w /usr/local/nagios/libexec/check_plugin -p wa -k nagios_checkplugin. Investigate any hit outside a planned upgrade. Also log execve with euid=0 spawned under getprofile.sh.
      • EDR process ancestry: Alert on the chain httpd/php-fpm → sudo → getprofile.sh → check_plugin → sh/bash/nc/python/perl running as uid 0. Sigma shape: ParentImage|endswith: '/check_plugin' AND Image|endswith: ['/bash','/sh','/nc','/python3'].
      • Network telemetry (Zeek/Suricata): Flag new outbound TCP sessions from the Nagios XI host to external IPs that aren't monitored targets, especially right after cmd=download requests. In Zeek conn.log, filter on id.orig_h == <nagiosxi> && !local_resp.
      • Authentication: Review admin logins from unusual networks in the Nagios XI audit log (Admin → Audit Log). Check /var/log/secure for sudo entries invoking getprofile.sh outside maintenance windows.

    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 before 5.6.6 allows remote command execution as root. The exploit requires access to the server as the nagios user, or access as the admin user via the web interface. The getprofile.sh script, invoked by downloading a system profile (profile.php?cmd=download), is executed as root via a passwordless sudo entry; the script executes check_plugin, which is owned by the nagios user. A user logged into Nagios XI with permissions to modify plugins, or the nagios user on the server, can modify the check_plugin executable and insert malicious commands to execute as root.

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

    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.6.6
    • 5.6.6

    Vendors and products

    Weakness classes (CWE)

    • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

      Base

      The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

      Entry at MITRE CWE-78

    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
    Reference tagged as exploitgithub.com (opens in a new tab)PoC (publicly reported)reported, not verified—
    Packet StormNagios XI Authenticated Remote Command Execution (opens in a new tab)packetstormsecurity.comPoC (publicly reported)reported, not verified—
    Packet StormNagios XI getprofile.sh Remote Command Execution (opens in a new tab)packetstormsecurity.comPoC (publicly reported)reported, not verified—

    References & sources

    • github.comjakgibb/nagiosxi-root-rce-exploitx_refsource_MISC, Exploit, Third-party advisory
    • packetstormsecurity.comfiles/156676/Nagios-XI-Authenticated-Remote-Command-Execution.h…x_refsource_MISC, Exploit, Third-party advisory, Vulnerability database
    • packetstormsecurity.comfiles/162158/Nagios-XI-getprofile.sh-Remote-Command-Execution.h…x_refsource_MISC, Exploit, Third-party advisory, Vulnerability database
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2019-15949government-resource, US government resource
    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-2019-15949
    <a href="https://intel.neosec.eu/en/cve/CVE-2019-15949"><img src="https://intel.neosec.eu/badge/cve/CVE-2019-15949.svg?lang=en" alt="CVE-2019-15949 – NEOSEC Intel" height="20"></a>