# CVE-2024-47575: Fortinet FortiManager Missing Authentication

> An attacker can execute arbitrary code or commands on FortiManager due to missing authentication for a critical function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:U/RC:C`)
- **Exploited in the wild:** Yes, since 23 Oct 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-hx4q-76p6-78cc

## What is CVE-2024-47575?

CVE-2024-47575 is a critical missing authorization vulnerability in Fortinet Fortimanager, published on 23 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authentication for critical function in FortiManager 7.6.0, FortiManager 7.4.0 through 7.4.4, FortiManager 7.2.0 through 7.2.7, FortiManager 7.0.0 through 7.0.12, FortiManager 6.4.0 through 6.4.14, FortiManager 6.2.0 through 6.2.12, Fortinet FortiManager Cloud 7.4.1 through 7.4.4, FortiManager Cloud 7.2.1 through 7.2.7, FortiManager Cloud 7.0.1 through 7.0.12, FortiManager Cloud 6.4.1 through 6.4.7 allows attacker to execute arbitrary code or commands via specially crafted requests.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-47575?

It affects 2 products.


Products: Fortinet Fortimanager, Fortinet Fortimanager Cloud.

## How do I fix CVE-2024-47575?

No fix has been published for CVE-2024-47575 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 13 Nov 2024.

## Is CVE-2024-47575 being exploited?

Yes. Attackers have exploited CVE-2024-47575 in the wild since at least 23 Oct 2024.

Public exploit code:

- Fortinet Fortimanager Unauthenticated Remote Code Execution AKA FortiJump CVE-2024-47575 (github_poc): https://github.com/watchtowrlabs/Fortijump-Exploit-CVE-2024-47575
- Fortinet FortiManager Unauthenticated RCE (metasploit)
- CVE POC Exploit (github_poc): https://github.com/revanslbw/CVE-2024-47575-POC
- PoC for CVE-2024-47575 (github_poc): https://github.com/AnnnNix/CVE-2024-47575

## Other vulnerabilities in Fortinet Fortimanager

- [CVE-2015-3613](https://insights.sbomify.com/CVE-2015-3613/): Privilege escalation in n/a (critical 9.8)
- [CVE-2019-6695](https://insights.sbomify.com/CVE-2019-6695/): Security feature bypass in Fortinet FortiManager (critical 9.8)
- [CVE-2019-17654](https://insights.sbomify.com/CVE-2019-17654/): Cross-site request forgery in Fortinet FortiManager (high 8.8)
- [CVE-2015-3611](https://insights.sbomify.com/CVE-2015-3611/): Command injection in n/a (high 8.8)
- [CVE-2023-42791](https://insights.sbomify.com/CVE-2023-42791/): Path traversal in FortiAnalyzer (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47575 and fix it if it is affected.

What it is: CVE-2024-47575 is a critical missing authorization vulnerability in Fortinet Fortimanager, published on 23 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-47575 in the wild since at least 23 Oct 2024.

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

## Sources

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

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