dbcve.org
Nagios XiApplication · Nagios

CVE-2016-15052

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 Menu System of the web interface. 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 · moderate confidence

Nagios XI versions before 5.2.4 contain a stored cross-site scripting (XSS) vulnerability in the Menu System component of the web interface. User-supplied input in the menu is not properly validated or escaped before being rendered, allowing injection of arbitrary JavaScript that executes in the context of other users' browsers.

MitigationUpgrade Nagios XI to version 5.2.4 or later to obtain the patch. If immediate upgrade is not feasible, implement output encoding and input validation on all menu-related user inputs as a compensating control.

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 Nagios XI installation
    Locate the Nagios XI installation directory, typically at /usr/local/nagiosxi/ or check for /opt/nagiosxi/. Look for the Nagios XI web interface accessible via HTTP/HTTPS.
    Affected if Nagios XI is installed and the web interface is accessible
  2. Determine installed Nagios XI version
    Check the version file at /usr/local/nagiosxi/etc/version.ini or access the web interface and look for the version information typically displayed in the footer or under 'Admin' > 'System Information'.
    Affected if The installed version is displayed and is below 5.2.4
  3. Compare version against affected range
    Parse the version number from step 2 and compare it numerically to 5.2.4. Any version < 5.2.4 (including 5.2.3, 5.2.0, 5.0.x, etc.) is affected.
    Affected if The installed version number is less than 5.2.4 (for example, 5.2.3, 5.2.0, or any 5.x.y version below 5.2.4)
  4. Verify Menu System component is in use
    Log into the Nagios XI web interface and navigate to the Menu System configuration (typically under 'Configure' > 'Menu' or similar menu management sections). Check if any custom menu items exist.
    Affected if The Menu System is accessible and configurable in the web interface (the vulnerability exists in this component regardless of whether custom menus are configured)

You are affected if Nagios XI is installed and the installed version is less than 5.2.4, as the stored XSS vulnerability exists in the Menu System component of all earlier versions.

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 Nagios XI to version 5.2.4 or later to obtain the patch. If immediate upgrade is not feasible, implement output encoding and input validation on all menu-related user inputs as a compensating control.

Recommended fix High confidence

5.2.4

  1. 1. Backup your current Nagios Xi installation and database before proceeding with the upgrade.
  2. 2. Download Nagios Xi version 5.2.4 from the official Nagios website (www.nagios.com).
  3. 3. Run the Nagios Xi upgrade wizard or use the command-line upgrade procedure appropriate for your installation.
  4. 4. After upgrade completion, verify the installation was successful by logging into the Nagios Xi web interface.
  5. 5. Confirm the XSS vulnerability is resolved by testing that user-supplied input in the Menu System is properly validated or escaped.

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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