dbcve.org
Nagios XiApplication · Nagios

CVE-2025-34283

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 XI versions prior to 2024R1.4.2 revealed API keys to users who were not authorized for API access when using Neptune themes. An authenticated user without API privileges could view another user's or their own API key value.

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 XI versions before 2024R1.4.2 contain a vulnerability in the Neptune theme where API keys are exposed to authenticated users who do not have API access privileges. The theme incorrectly renders API key values for unauthorized users, allowing them to view their own or other users' API keys.

MitigationUpgrade to Nagios XI 2024R1.4.2 or later. If immediate upgrade is not feasible, consider disabling the Neptune theme or restricting user access pending the patch.

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
Nagios XiApplication
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 Nagios XI version
    Access the Nagios XI administration interface and navigate to the 'About' or 'System Information' page to view the installed version number
    Affected if The installed version is before 2024R1.4.2 (e.g., 2024R1.0, 2023R1.x, etc.)
  2. Confirm Neptune theme is active
    Log into Nagios XI and check the current theme setting in the user preferences or system configuration. The Neptune theme is typically selectable under 'System' > 'General' > 'Default Theme' or user profile settings
    Affected if The Neptune theme is selected and active for the logged-in user
  3. Verify user lacks API access privileges
    Navigate to 'Admin' > 'User Management' > 'Users' and check the permissions assigned to the current user account. Look for whether the 'API Access' or 'Nagios XI API' permission is granted to the user
    Affected if The user is authenticated but does not have API access privileges enabled in their user account settings
  4. Test for API key exposure
    As the unprivileged user, navigate to their own user profile page or the 'My Account' section. Look for any field that displays or renders an API key value. Also check other users' profiles if admin-level access allows viewing user lists
    Affected if API key values are visible or rendered in the UI for a user who does not have API access privileges

A user is affected if running Nagios XI before 2024R1.4.2, the Neptune theme is active, and API keys are displayed to authenticated users who lack API access permissions.

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 XI 2024R1.4.2 or later. If immediate upgrade is not feasible, consider disabling the Neptune theme or restricting user access pending the patch.

Recommended fix High confidence

2024R1.4.2 or later

  1. Identify current Nagios XI version via the web interface (About page) or by checking the version file
  2. Confirm the version is affected: prior to 2024R1.4.2 or exactly version 2024
  3. Review and follow Nagios XI backup procedures to create a full backup before upgrading
  4. Upgrade to version 2024R1.4.2 or later by following the official Nagios XI upgrade documentation at docs.nagios.com
  5. After upgrade, verify the vulnerability is remediated by testing that authenticated users without API privileges can no longer view API key values in the Neptune theme
  6. Clear any cached data and session information to ensure the fix takes effect
Caveat Standard Nagios XI upgrade risks apply - test in staging first, ensure backups exist, and review upgrade documentation for any specific prerequisites

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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