dbcve.org
FusionApplication · Nagios

CVE-2025-60425

HIGH · 8.6 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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 Fusion v2024R1.2 and v2024R2 does not invalidate already existing session tokens when the two-factor authentication mechanism is enabled, allowing attackers to perform a session hijacking attack.

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 Fusion versions 2024R1.2 and 2024R2 fail to invalidate existing session tokens when two-factor authentication is enabled. This allows an attacker with a previously valid session token to maintain access even after the account owner enables 2FA, effectively bypassing the additional security layer through session hijacking.

MitigationEnable 2FA for affected accounts and force re-authentication to establish new sessions; consider implementing session invalidation on 2FA enablement via vendor 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
FusionApplication
Affected:= 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
Low
Integrity
High
Availability
Low

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

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 Fusion installation and version
    Check the installed Nagios Fusion version via the web interface (Help > About) or by inspecting version files in the installation directory such as /usr/local/nagios/fusion/ or /opt/nagios/fusion/
    Affected if The installed version is 2024 (specifically 2024R1.2 or 2024R2)
  2. Verify if 2FA is enabled for any user accounts
    Access the Nagios Fusion admin panel and navigate to Account Settings or User Management to check if Two-Factor Authentication is enabled for any accounts
    Affected if 2FA is enabled on any user account in the system
  3. Assess session validity context
    Determine whether user sessions existed prior to 2FA being enabled - the vulnerability allows pre-existing sessions to remain valid even after 2FA is activated
    Affected if 2FA was recently enabled on an account that had active sessions before 2FA was turned on

You are affected if running Nagios Fusion version 2024 (2024R1.2 or 2024R2) and 2FA has been enabled on any account that had sessions active before 2FA was enabled, because those old sessions remain valid and can bypass the 2FA requirement.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable 2FA for affected accounts and force re-authentication to establish new sessions; consider implementing session invalidation on 2FA enablement via vendor patch.

Recommended fix Moderate confidence

Latest Nagios Fusion 2024 release (post-v2024R2) or 2025 release

  1. 1. Identify the current Nagios Fusion version in use (2024R1.2 or 2024R2)
  2. 2. Navigate to the Nagios Fusion downloads page at www.nagios.com/downloads/nagios-fusion
  3. 3. Download the latest stable release of Nagios Fusion
  4. 4. Review the release notes for the new version to confirm the session handling fix is included
  5. 5. Backup the current Nagios Fusion configuration and database before upgrading
  6. 6. Install the updated Nagios Fusion package using standard upgrade procedures
  7. 7. After upgrade, verify that existing sessions are properly invalidated when 2FA is toggled
  8. 8. Confirm all users re-authenticate with 2FA after the upgrade
Caveat Standard upgrade risk: review compatibility notes and ensure backup before proceeding

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

Fix this in Fusion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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