dbcve.org
Nagios XiApplication · Nagios

CVE-2016-15050

HIGH · 8.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.2.4 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.2.4 contain a SQL injection vulnerability in the notification search functionality. User-supplied search parameters were incorporated into SQL statements without adequate parameterization or sanitation, allowing an authenticated user to manipulate database queries. Successful exploitation could disclose or modify notification data and, in some cases, impact the application database more broadly.

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 5.2.4 contain an authenticated SQL injection vulnerability in the notification search functionality. User-supplied search parameters are incorporated directly into SQL statements without proper parameterization, allowing authenticated attackers to manipulate database queries. This can lead to unauthorized disclosure or modification of notification data and potentially broader database compromise.

MitigationUpgrade to Nagios XI version 5.2.4 or later which contains the patched code. As a compensating control, restrict access to the notification search functionality to trusted administrators until the upgrade can be completed.

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.2.4

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. Determine installed Nagios XI version
    Log into the Nagios XI administrative interface and navigate to the 'About' or 'System Information' page typically found under the 'Admin' or 'Settings' menu. Alternatively, check the file '/usr/local/nagiosxi/etc/xi-sys.cfg' or run the command 'cat /usr/local/nagiosxi/etc/xi-version' from the server console.
    Affected if The displayed version number is less than 5.2.4 (for example, 5.2.3, 5.2.0, or any 5.x version prior to 5.2.4)
  2. Verify notification search functionality is accessible
    Locate the notification search feature in the Nagios XI web interface, typically found under 'Notifications' or 'Reporting' sections. Determine if this feature is enabled and accessible to any user account.
    Affected if The notification search functionality is enabled and available in the web interface
  3. Identify authenticated user accounts
    Review the Nagios XI user management section under 'Admin' > 'User Settings' or 'User Management' to list all configured user accounts that have access to the system.
    Affected if There exists at least one active authenticated user account with access to the notification search feature

A system is affected if it is running Nagios XI version prior to 5.2.4 AND the notification search functionality is accessible to any authenticated user.

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.2.4 or later
Fixed in 5.2.4
Interim mitigation

Upgrade to Nagios XI version 5.2.4 or later which contains the patched code. As a compensating control, restrict access to the notification search functionality to trusted administrators until the upgrade can be completed.

Recommended fix Moderate confidence

5.2.4

  1. Back up the current Nagios XI installation and database before proceeding with any upgrade
  2. Download Nagios XI version 5.2.4 or later from the official Nagios download portal (www.nagios.com)
  3. Extract the downloaded archive and navigate to the upgrade directory
  4. Run the upgrade script as root: ./upgrade xi
  5. Follow the on-screen prompts to complete the upgrade process
  6. After upgrade completion, verify the Nagios XI services are running: systemctl status nagios xi
  7. Log in to the Nagios XI web interface and navigate to the notification search functionality to confirm the vulnerability is remediated
  8. Review the upgrade logs in /var/log/nagiosxi/upgrade.log for any errors
Caveat Review Nagios XI 5.2.4 release notes for any configuration or feature changes before upgrading in production environments

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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