dbcve.org
Log ServerApplication · Nagios

CVE-2025-34273

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
Nagios Log Server versions prior to 2024R2.0.3 contain an incorrect authorization vulnerability that allows non-administrator users to delete global dashboards. The application did not correctly enforce authorization checks for the global dashboard deletion workflow, enabling lower-privileged users to remove dashboards that affect other users or the overall monitoring UI.

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 Log Server versions prior to 2024R2.0.3 contain an incorrect authorization vulnerability in the global dashboard deletion workflow. The application fails to properly enforce authorization checks, allowing authenticated non-administrator users to delete global dashboards that affect other users and the overall monitoring UI.

MitigationUpgrade Nagios Log Server to version 2024R2.0.3 or later to obtain the patched authorization controls.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Nagios Log Server version
    Access the Nagios Log Server admin interface or check the installed package/version information to determine the current software version
    Affected if The installed version is any release prior to 2024R2.0.3, including all 2024.x versions before 2024R2.0.3
  2. Confirm global dashboard functionality exists
    Navigate to the dashboard management section of the Nagios Log Server interface and verify that global dashboards can be created or managed
    Affected if Global dashboard functionality is present and accessible within the application
  3. Review user role assignments
    Check the user management or authentication settings to identify what roles are assigned to non-administrator users in the system
    Affected if There are authenticated users with non-administrator roles in the system
  4. Verify authorization controls on dashboard deletion
    Attempt to access the global dashboard deletion workflow using a non-administrator account, or review the authorization configuration for the dashboard deletion endpoint
    Affected if Non-administrator users can access or execute global dashboard deletion operations without proper authorization checks

A user is affected if they are running Nagios Log Server version 2024.x prior to 2024R2.0.3 (or any version before 2024) and have non-administrator user accounts that could potentially delete global dashboards due to missing authorization enforcement.

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 Nagios Log Server to version 2024R2.0.3 or later to obtain the patched authorization controls.

Recommended fix Moderate confidence

2024R2.0.3

  1. 1. Back up the current Nagios Log Server configuration and data
  2. 2. Download the latest Nagios Log Server version 2024R2.0.3 from the official Nagios website (www.nagios.com)
  3. 3. Follow the standard Nagios Log Server upgrade procedure for your installation method (ZIP archive or VM appliance)
  4. 4. Verify the upgrade completed successfully by logging into the web interface
  5. 5. Confirm that the authorization fix is in place by testing that non-administrator users can no longer delete global dashboards

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

Fix this in Log Server 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-2025-34273 — 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-34273 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