dbcve.org
Network AnalyzerApplication · Nagios

CVE-2023-7319

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 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 Network Analyzer versions prior to 2024R1 are vulnerable to cross-site scripting (XSS) via the Percentile Calculator menu. 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 Network Analyzer versions prior to 2024R1 contain a stored XSS vulnerability in the Percentile Calculator menu where user-supplied input is not properly validated or escaped, allowing injection of arbitrary JavaScript that executes in victims' browsers when the malicious input is rendered.

MitigationUpgrade to version 2024R1 or later, or implement proper input validation and output encoding when rendering user-supplied data in the Percentile Calculator feature.

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
Network AnalyzerApplication
Affected:< 2024

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 installed Nagios Network Analyzer version
    Access the Nagios Network Analyzer web interface and navigate to Admin > System Information, or check the version via the backend using 'rpm -q nagiosna' or similar package query command depending on your installation method
    Affected if The installed version is prior to 2024R1 (versions like 2023.x, 2022.x, etc.)
  2. Confirm Percentile Calculator feature access
    Log into the web interface and locate the Percentile Calculator menu option, typically found under the Reports or Tools section
    Affected if The Percentile Calculator feature is accessible and enabled in the installation
  3. Review stored input in Percentile Calculator
    If you have access to the backend database, query the tables related to the Percentile Calculator feature for any stored input that may contain script tags or unusual characters (e.g., <script>, javascript:, onload=, onerror=)
    Affected if Suspicious or unsanitized input containing HTML/script tags is found stored in the Percentile Calculator data storage

Your environment is affected if Nagios Network Analyzer version is prior to 2024R1 AND the Percentile Calculator feature is in use AND unsanitized user input exists in that feature.

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 2024 or later
Fixed in 2024
Interim mitigation

Upgrade to version 2024R1 or later, or implement proper input validation and output encoding when rendering user-supplied data in the Percentile Calculator feature.

Recommended fix High confidence

Nagios Network Analyzer 2024R1

  1. Back up current Nagios Network Analyzer configuration, database, and all relevant data
  2. Download Nagios Network Analyzer 2024R1 (or latest version) from the official Nagios website (www.nagios.com)
  3. Review the official Nagios upgrade documentation for Network Analyzer
  4. Stop the Nagios Network Analyzer services before upgrading
  5. Install the 2024R1 version following the documented upgrade procedure
  6. Restart the Nagios Network Analyzer services after installation
  7. Verify the upgrade was successful by checking the version in the web interface
  8. Confirm the Percentile Calculator functionality works correctly and the XSS vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Network Analyzer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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