# CVE-2025-60424: Auth bypass in n/a

> Attackers can bypass authentication in Nagios Fusion by brute-forcing OTP codes due to missing rate limiting, leading to unauthorized access.

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** CVE-2025-34269, GHSA-f8r7-6gm2-hh64

## What is CVE-2025-60424?

CVE-2025-60424 is a high-severity authentication bypass vulnerability in n/a, published on 27 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A lack of rate limiting in the OTP verification component of Nagios Fusion v2024R1.2 and v2024R2 allows attackers to bypass authentication via a bruteforce attack.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-60424?

It affects 1 product.


Products: Nagios Fusion.

## How do I fix CVE-2025-60424?

No fix has been published for CVE-2025-60424 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-60424 being exploited?

There is no known exploitation of CVE-2025-60424 in the wild and no public exploit code.

Public exploit code:

- https://github.com/aakashtyal/2FA-Bypass-using-a-Brute-Force-Attack-CVE-2025-60424 (github_poc): https://github.com/aakashtyal/2FA-Bypass-using-a-Brute-Force-Attack-CVE-2025-60424

## Other vulnerabilities in n/a

- [CVE-2020-28900](https://insights.sbomify.com/CVE-2020-28900/): Code injection in n/a (critical 9.8)
- [CVE-2020-28901](https://insights.sbomify.com/CVE-2020-28901/): Command injection in n/a (critical 9.8)
- [CVE-2020-28902](https://insights.sbomify.com/CVE-2020-28902/): Command injection in n/a (critical 9.8)
- [CVE-2020-28904](https://insights.sbomify.com/CVE-2020-28904/): Privilege escalation in n/a (critical 9.8)
- [CVE-2020-28907](https://insights.sbomify.com/CVE-2020-28907/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60424 and fix it if it is affected.

What it is: CVE-2025-60424 is a high-severity authentication bypass vulnerability in n/a, published on 27 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60424 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-60424/ (Markdown: https://insights.sbomify.com/CVE-2025-60424/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-60424
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-60424
- OSV: https://osv.dev/vulnerability/CVE-2025-60424

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-60424/
Summaries are generated and may contain mistakes; the official description above is the record.