dbcve.org
Log ServerApplication · Nagios

CVE-2025-34272

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
In Nagios Log Server versions prior to 2024R2.0.3, when a user's configured default dashboard is deleted, the application does not reliably fall back to an empty, default dashboard. In some implementations this can result in an unexpected dashboard being presented as the user's default view. Depending on the product's dashboard sharing and access policies, this behavior may cause information exposure or unexpected privilege exposure.

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

In Nagios Log Server versions prior to 2024R2.0.3, when a user's configured default dashboard is deleted, the application fails to reliably fall back to a safe, empty default dashboard. Instead, it may display an unexpected dashboard (likely a previously accessed or shared dashboard), leading to potential information exposure or privilege escalation if that dashboard has broader access permissions than intended.

MitigationUpgrade to Nagios Log Server 2024R2.0.3 or later. As interim mitigation, audit user dashboard configurations to ensure no deleted dashboards are set as defaults, and review dashboard sharing policies to limit exposure from unexpected dashboard access.

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
Log ServerApplication
Affected:< 2024= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the installed Nagios Log Server version
    Locate the version file or use the system information command for Nagios Log Server (typically in /usr/local/nagios/logserver or via 'nls --version' or checking the web interface footer)
    Affected if The installed version is any release prior to 2024R2.0.3, including all 2024 releases and versions before 2024
  2. Check user default dashboard configurations
    Access the user preference settings in the Nagios Log Server database or configuration files where default dashboard assignments are stored (often in the users or preferences table)
    Affected if Any user account has a default dashboard explicitly configured
  3. Verify if configured default dashboards still exist
    Compare the list of user-assigned default dashboards against the currently active dashboards in the system, checking for any assigned defaults that have been deleted from the dashboard repository
    Affected if A user's default dashboard reference points to a deleted or non-existent dashboard
  4. Audit dashboard access patterns for unexpected exposure
    Review dashboard access logs or audit trails to identify if users are viewing dashboards they did not intentionally select, especially after a dashboard deletion event
    Affected if Users are being routed to dashboards different from their configured default, indicating the fallback mechanism is behaving unexpectedly

A user is affected if they run Nagios Log Server versions before 2024R2.0.3 and have a default dashboard configured that was subsequently deleted, causing potential exposure to unexpected dashboards.

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 Nagios Log Server 2024R2.0.3 or later. As interim mitigation, audit user dashboard configurations to ensure no deleted dashboards are set as defaults, and review dashboard sharing policies to limit exposure from unexpected dashboard access.

Recommended fix High confidence

2024R2.0.3

  1. Identify the current Nagios Log Server version running in your environment
  2. Create a full backup of the Nagios Log Server configuration and data
  3. Upgrade Nagios Log Server to version 2024R2.0.3 or later
  4. After upgrade, verify the application is running correctly
  5. Test the dashboard fallback behavior by creating a user with a default dashboard, then deleting that dashboard to confirm it falls back to an empty default view instead of exposing other dashboards

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

Fix this in Log Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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