# CVE-2025-54820: Memory corruption in FortiManager

> Remote unauthenticated attackers can execute unauthorized commands via crafted requests if the service is enabled, bypassing stack protections.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-qq5m-xh4x-hv7f

## What is CVE-2025-54820?

CVE-2025-54820 is a high-severity memory corruption vulnerability in Fortinet Fortimanager, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Stack-based Buffer Overflow vulnerability [CWE-121] vulnerability in Fortinet FortiManager 7.4.0 through 7.4.2, FortiManager 7.2.0 through 7.2.10, FortiManager 6.4 all versions may allow a remote unauthenticated attacker to execute unauthorized commands via crafted requests, if the service is enabled. The success of the attack depends on the ability to bypass the stack protection mechanisms.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Fortinet Fortimanager.

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

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

## Is CVE-2025-54820 being exploited?

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

## Other vulnerabilities in Fortinet Fortimanager

- [CVE-2024-47575](https://insights.sbomify.com/CVE-2024-47575/): Fortinet FortiManager Missing Authentication (critical 9.8, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54820 is a high-severity memory corruption vulnerability in Fortinet Fortimanager, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54820 in the wild and no public exploit code.

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-2025-54820/ (Markdown: https://insights.sbomify.com/CVE-2025-54820/index.md)
```

## Sources

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

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