# CVE-2025-59808: Auth bypass in FortiSOAR PaaS

> An attacker with existing account access can reset credentials without password verification, leading to account takeover in FortiSOAR.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H/E:H/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-787x-8wcq-jhq8

## What is CVE-2025-59808?

CVE-2025-59808 is a medium-severity authentication bypass vulnerability in Fortinet FortiSOAR PaaS, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An unverified password change vulnerability [CWE-620] vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.2, FortiSOAR PaaS 7.5.0 through 7.5.1, FortiSOAR PaaS 7.4 all versions, FortiSOAR PaaS 7.3 all versions, FortiSOAR on-premise 7.6.0 through 7.6.2, FortiSOAR on-premise 7.5.0 through 7.5.1, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow an attacker who has already gained access to a victim's user account to reset the account credentials without being prompted for the account's password

Weakness: CWE-620 (Unverified Password Change)

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

It affects 1 product.


Products: Fortinet Fortisoar.

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

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

## Is CVE-2025-59808 being exploited?

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

## Other vulnerabilities in Fortinet FortiSOAR PaaS

- [CVE-2024-47572](https://insights.sbomify.com/CVE-2024-47572/): Code injection in FortiSOAR (high 8.3)
- [CVE-2024-21760](https://insights.sbomify.com/CVE-2024-21760/): Code injection in FortiSOAR (high 7.7)
- [CVE-2023-25605](https://insights.sbomify.com/CVE-2023-25605/): Missing authorization in FortiSOAR (high 7.5)
- [CVE-2022-23443](https://insights.sbomify.com/CVE-2022-23443/): Missing authorization in Fortinet FortiSOAR (high 7.5)
- [CVE-2023-27995](https://insights.sbomify.com/CVE-2023-27995/): Code injection in FortiSOAR (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59808 is a medium-severity authentication bypass vulnerability in Fortinet FortiSOAR PaaS, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59808 in the wild and no public exploit code.

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

## Sources

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

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