CVE-2025-34278
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 · uneditedNagios Network Analyzer versions prior to 2024R1 contain a stored cross-site scripting (XSS) vulnerability in the Source Groups page (percentile calculator menu). An attacker can supply a malicious payload which is stored by the application and later rendered in the context of other users. When a victim views the affected page the injected script executes in the victim's browser context.
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 confidenceNagios Network Analyzer versions prior to 2024R1 contain a stored XSS vulnerability in the Source Groups page's percentile calculator menu. Attackers can inject malicious JavaScript payloads that persist in the application and execute in the browsers of users who view the affected page.
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< 2024CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine Nagios Network Analyzer versionLocate the installed Nagios Network Analyzer version number via the web interface (typically in Help > About) or by checking version files in the installation directoryAffected if The installed version is any release prior to 2024R1 (e.g., 2023.x, 2022.x, etc.)
-
Verify Source Groups module is accessibleNavigate to the Source Groups page in the Nagios Network Analyzer web interface - this is typically found under the 'Reports' or 'Sources' menu sectionAffected if The Source Groups page loads and is accessible to the user account being tested
-
Confirm percentile calculator feature existsLocate the percentile calculator menu/option within the Source Groups page interface - this is typically a dropdown, input field, or calculation tool for percentile analysisAffected if The percentile calculator functionality is present and accepts user input
-
Test for XSS persistence in percentile calculatorEnter a benign XSS test payload (such as <script>alert('XSS')</script> or similar) into the percentile calculator input fields, save the configuration, then navigate away and return to the page to verify if the payload persists and executesAffected if The submitted payload is reflected back in the page source without proper encoding and executes when the page loads
A user is affected if their Nagios Network Analyzer version is prior to 2024R1 AND they have access to the Source Groups page with an active percentile calculator that accepts and reflects unsanitized input.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024
Upgrade to Nagios Network Analyzer 2024R1 or later. As a temporary workaround, implement input validation and output encoding on the percentile calculator functionality.
2024R1
- 1. Back up the current Nagios Network Analyzer installation and configuration data.
- 2. Download the Nagios Network Analyzer 2024R1 release from the official Nagios website (www.nagios.com).
- 3. Review the official upgrade documentation for Nagios Network Analyzer 2024R1.
- 4. Execute the upgrade installer according to the provided upgrade procedures.
- 5. Verify that the upgrade completed successfully by logging into the web interface.
- 6. Navigate to the Source Groups page (percentile calculator menu) to confirm the vulnerability is remediated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-34278 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34278 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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