dbcve.org
Log ServerApplication · Nagios

CVE-2025-34277

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 2024R1.3.1 contain a code injection vulnerability where malformed dashboard ID values are not properly validated before being forwarded to an internal API. An attacker able to supply crafted dashboard ID values can cause the system to execute attacker-controlled data, leading to arbitrary code execution in the context of the Log Server process.

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 2024R1.3.1 fail to validate dashboard ID values before passing them to an internal API, allowing injection of attacker-controlled data that gets executed by the system, leading to arbitrary code execution in the context of the Log Server process.

MitigationUpgrade to Nagios Log Server 2024R1.3.1 or later to obtain the patched version that properly validates dashboard ID values.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installation
    Locate the Nagios Log Server installation directory or check the web interface footer for the version number. On Linux systems, also run: rpm -q nagioslogserver or dpkg -l | grep nagioslogserver
    Affected if The installed version cannot be determined or is earlier than 2024R1.3.1
  2. Verify dashboard functionality is accessible
    Check if the Nagios Log Server web interface dashboard feature is accessible by navigating to the dashboard section or checking if /dashboard endpoint responds
    Affected if The dashboard interface is accessible without additional authentication barriers
  3. Check internal API endpoint exposure
    Inspect web server configuration files (typically in /usr/local/nagioslogserver/nginx/conf/ or /etc/nagioslogserver/) for the API endpoint handling dashboard IDs. Look for routes like /api/dashboard or similar internal API paths
    Affected if The internal API accepts dashboard ID parameters without validation
  4. Confirm version falls within affected range
    Compare your installed version against the affected range: any version prior to 2024, or version 2024 (any sub-version), or versions earlier than 2024R1.3.1
    Affected if The installed version is 2024.x or any version before 2024R1.3.1

You are affected if the installed Nagios Log Server version is 2024.x or any version prior to 2024R1.3.1 and the dashboard feature is accessible.

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 2024R1.3.1 or later to obtain the patched version that properly validates dashboard ID values.

Recommended fix High confidence

2024R1.3.1 or later

  1. Identify the current Nagios Log Server version by checking the About or System Information page in the web interface, or by running the appropriate version command
  2. Backup all Nagios Log Server configurations, databases, and any custom settings before proceeding with the upgrade
  3. Download Nagios Log Server version 2024R1.3.1 or later from the official Nagios website (www.nagios.com)
  4. Follow the official Nagios upgrade documentation to install the fixed version, ensuring to preserve existing configurations during the upgrade process
  5. After upgrade completion, verify the installation was successful by checking the version number
  6. Test that the dashboard functionality works correctly and the code injection vulnerability is no longer present

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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