dbcve.org
Nagios XiApplication · Nagios

CVE-2023-7314

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) via the Bandwidth Report component. 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.11.3 contain a stored XSS vulnerability in the Bandwidth Report component. The application fails to properly validate or escape user-supplied input, allowing an attacker to inject malicious JavaScript that executes in the context of other users' browsers.

MitigationUpgrade to Nagios XI version 5.11.3 or later, or implement proper input validation and output encoding on the Bandwidth Report 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. Check Nagios XI version
    Navigate to the Nagios XI admin interface, typically at /nagiosxi/ or /nagios/. Look for the version information in the About page or footer of the admin dashboard. Alternatively, check the file /usr/local/nagiosxi/etc/constants.php or run: grep 'XI_VERSION' /usr/local/nagiosxi/etc/constants.php
    Affected if The installed version is below 5.11.3 (any version from the Nagios XI 5.x series prior to 5.11.3)
  2. Identify Bandwidth Report component access
    Log into the Nagios XI web interface and locate the Bandwidth Report component. This is typically found under the Reports or Tools section in the navigation menu. Check if you have access to this feature by attempting to access it or reviewing user permissions.
    Affected if The Bandwidth Report component is available and accessible to users in your environment
  3. Verify Bandwidth Report input handling
    Access the Bandwidth Report functionality and examine how user input is handled. Look for input fields related to bandwidth reporting such as host selection, time range, or other parameters. Attempt to identify if these inputs are reflected back in the application without visible sanitization.
    Affected if User-supplied input in the Bandwidth Report is reflected in the application output without proper encoding or validation
  4. Review user roles and permissions
    Check the Nagios XI user management panel to see which users or user groups have access to the Bandwidth Report component. This helps determine the potential attack surface for stored XSS.
    Affected if Multiple users have access to the Bandwidth Report component, increasing the risk of stored XSS being triggered

You are affected if your Nagios XI installation is version 5.11.3 or lower AND the Bandwidth Report component is accessible to users in your environment.

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 version 5.11.3 or later, or implement proper input validation and output encoding on the Bandwidth Report component.

Recommended fix High confidence

5.11.3

  1. Upgrade Nagios XI to version 5.11.3 or later
  2. Verify the upgrade was successful by checking the Nagios XI version
  3. Test the Bandwidth Report component to confirm the XSS vulnerability is remediated

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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