dbcve.org
Nagios XiApplication · Nagios

CVE-2023-53688

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 5.11.3 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.11.3 are vulnerable to cross-site scripting (XSS) and cross-site request forgery (CSRF) via the Hypermap Replay component. An attacker can submit crafted input that is not properly validated or escaped, allowing injection of malicious script that executes in the context of a victim's browser (XSS). Additionally, the component does not enforce sufficient anti-CSRF protections on state-changing operations, enabling an attacker to induce authenticated users to perform unwanted actions.

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.11.3 contain a combined XSS and CSRF vulnerability in the Hypermap Replay component. Attackers can inject malicious script through unsanitized user input that executes in authenticated users' browsers, while the lack of anti-CSRF protections allows attackers to trick authenticated users into performing unintended state-changing actions.

MitigationUpgrade to Nagios XI 5.11.3 or later, which includes proper input validation, output encoding, and anti-CSRF token implementation for the Hypermap Replay component.

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

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. Determine Nagios XI version
    Run the following command to check the installed Nagios XI version: cat /usr/local/nagxi/etc/.build_info or check the Nagios XI admin interface under 'Admin > System Information'. Compare the version number to the affected range (< 5.11.3).
    Affected if The installed version is below 5.11.3 (e.g., 5.11.2, 5.11.1, 5.10.x, etc.)
  2. Identify if Hypermap Replay component is installed
    Check for the presence of the Hypermap Replay module in the Nagios XI installation. Look for files or directories related to 'hypermap' or 'replay' under /usr/local/nagiosxi/, or check the list of enabled components in the Nagios XI admin interface under 'Admin > System Extensions > Manage Components'.
    Affected if The Hypermap Replay component is installed and enabled on the system
  3. Verify anti-CSRF protection status in Hypermap Replay
    Examine the source code or configuration files for the Hypermap Replay component to determine if anti-CSRF tokens are implemented. This typically involves checking form submissions and AJAX requests within the hypermap module for the presence of token validation logic.
    Affected if Anti-CSRF token validation is missing from the Hypermap Replay component requests
  4. Inspect Hypermap Replay input handling
    Review the Hypermap Replay component code for input sanitization. Check how user-supplied data (such as map coordinates, labels, or replay parameters) is processed and whether output encoding is applied before rendering in the browser.
    Affected if User input in the Hypermap Replay component is not properly sanitized or encoded before display

A user is affected if they are running any Nagios XI version below 5.11.3 with the Hypermap Replay component enabled, as both conditions are required for the XSS and CSRF vulnerabilities to be exploitable.

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.11.3 or later
Fixed in 5.11.3
Interim mitigation

Upgrade to Nagios XI 5.11.3 or later, which includes proper input validation, output encoding, and anti-CSRF token implementation for the Hypermap Replay component.

Recommended fix High confidence

5.11.3

  1. Back up the current Nagios XI installation and database before proceeding with any upgrade
  2. Download Nagios XI version 5.11.3 from the official Nagios website (www.nagios.com)
  3. Run the official Nagios XI upgrade installer to update to version 5.11.3
  4. Follow standard Nagios XI post-upgrade procedures to ensure all services restart correctly
  5. Verify the Hypermap Replay component is functioning properly after the upgrade
  6. Confirm the XSS and CSRF vulnerabilities are remediated by testing the affected component

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-2023-53688 — 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-2023-53688 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