# CVE-2025-24472: Fortinet FortiOS and FortiProxy Authentication Bypass

> Remote attackers can gain super-admin privileges on FortiOS or FortiProxy devices via crafted requests if Security Fabric is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 18 Mar 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-rp3f-whm7-36hq

## What is CVE-2025-24472?

CVE-2025-24472 is a high-severity authentication bypass vulnerability in Fortinet Fortios, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] affecting FortiOS 7.0.0 through 7.0.16 and FortiProxy 7.2.0 through 7.2.12, 7.0.0 through 7.0.19 may allow a remote unauthenticated attacker with prior knowledge of upstream and downstream devices serial numbers to gain super-admin privileges on the downstream device, if the Security Fabric is enabled, via crafted CSF proxy requests.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 2 products.


Products: Fortinet Fortios, Fortinet Fortiproxy.

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

No fix has been published for CVE-2025-24472 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 Apr 2025.

## Is CVE-2025-24472 being exploited?

Yes. Attackers have exploited CVE-2025-24472 in the wild since at least 18 Mar 2025, including in ransomware campaigns.

Public exploit code:

- CVE Reproduction: cve-2025-24472-fortinet_authbypass_reproduction (github_poc): https://github.com/razureink/cve-2025-24472-fortinet_authbypass_reproduction

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24472 is a high-severity authentication bypass vulnerability in Fortinet Fortios, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-24472 in the wild since at least 18 Mar 2025, including in ransomware campaigns.

Affected product: Fortinet Fortios. 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-24472/ (Markdown: https://insights.sbomify.com/CVE-2025-24472/index.md)
```

## Sources

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

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