dbcve.org
Nagios XiApplication · Nagios

CVE-2016-15051

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.2.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 are vulnerable to cross-site scripting (XSS) via the Reports interface through values from the startdate and enddate fields. Insufficient validation or escaping of user-supplied input may allow an attacker to inject and execute arbitrary script in the context of a victim's browser.

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 before 5.2.4 contain a stored XSS vulnerability in the Reports interface. The startdate and enddate parameters are not properly validated or escaped, allowing attackers to inject malicious JavaScript that executes in victims' browsers when they view compromised reports.

MitigationUpgrade to Nagios XI 5.2.4 or later, which includes proper input validation and output encoding for the date fields in the Reports interface.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 if Nagios XI is installed
    Look for Nagios XI installation directories such as /usr/local/nagiosxi, /opt/nagiosxi, or check for the nagiosxi service/process running
    Affected if Nagios XI software is not present on the system
  2. Determine the installed Nagios XI version
    Check the version file typically located at /usr/local/nagiosxi/etc/xi-version.txt or access the Admin > System Info page in the web interface
    Affected if The installed version is lower than 5.2.4 (e.g., 5.2.3, 5.2.0, 5.0.x, etc.)
  3. Verify the Reports module is enabled and accessible
    Log into the Nagios XI web interface and navigate to the Reports section, or check that the reports CGI is present in /usr/local/nagiosxi/html/
    Affected if The Reports interface is accessible and users can create or view reports
  4. Inspect report configurations for suspicious date parameter values
    Examine the Nagios XI database (typically MySQL/MariaDB) in the xiReports* tables or check report configuration files in /usr/local/nagiosxi/etc/ for unescaped HTML/JavaScript in startdate or enddate fields
    Affected if Malicious JavaScript code is found stored in date-related fields within report configurations
  5. Check for stored XSS artifacts in browser sessions
    Review saved browser bookmarks or cached pages of the Reports interface for unexpected script tags or event handlers in URL parameters
    Affected if Users accessing the Reports interface have experienced unexpected script execution in their browsers

A system is affected if Nagios XI versions below 5.2.4 are installed AND the Reports interface is accessible, allowing stored XSS payloads in startdate/enddate parameters to execute when users view reports.

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 5.2.4 or later, which includes proper input validation and output encoding for the date fields in the Reports interface.

Recommended fix High confidence

5.2.4

  1. Back up the Nagios XI installation and database before upgrading
  2. Upgrade to Nagios XI version 5.2.4 or later
  3. Verify the upgrade was successful and test that the XSS vulnerability is resolved

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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