# CVE-2025-52970: Privilege escalation in FortiWeb

> Unauthenticated remote attackers can gain admin privileges on FortiWeb devices via specially crafted requests exploiting improper parameter handling.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2025
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-jc24-hjq6-4g6f

## What is CVE-2025-52970?

CVE-2025-52970 is a high-severity vulnerability in Fortinet Fortiweb, published on 12 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A improper handling of parameters in Fortinet FortiWeb versions 7.6.3 and below, versions 7.4.7 and below, versions 7.2.10 and below, and 7.0.10 and below may allow an unauthenticated remote attacker with non-public information pertaining to the device and targeted user to gain admin privileges on the device via a specially crafted request.

Weakness: CWE-233 (Improper Handling of Parameters)

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

It affects 1 product.


Products: Fortinet Fortiweb.

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

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

## Is CVE-2025-52970 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52970 exists.

Public exploit code:

- https://github.com/Hex00-0x4/FortiWeb-CVE-2025-52970-Authentication-Bypass (github_poc): https://github.com/Hex00-0x4/FortiWeb-CVE-2025-52970-Authentication-Bypass
-  CVE-2025-52970 - FortiWeb Authentication Bypass to Remote Code Execution Exploit  (github_poc): https://github.com/34zY/CVE-2025-52970
- https://github.com/imbas007/POC-CVE-2025-52970 (github_poc): https://github.com/imbas007/POC-CVE-2025-52970
- Fortinet FortiWeb - Authentication Bypass to Admin Privilege (nuclei): http/cves/2025/CVE-2025-52970.yaml

## Other vulnerabilities in Fortinet Fortiweb

- [CVE-2025-25257](https://insights.sbomify.com/CVE-2025-25257/): Fortinet FortiWeb SQL Injection (critical 9.6, exploited in the wild)
- [CVE-2025-64446](https://insights.sbomify.com/CVE-2025-64446/): Fortinet FortiWeb Path Traversal (critical 9.4, exploited in the wild)
- [CVE-2025-58034](https://insights.sbomify.com/CVE-2025-58034/): Fortinet FortiWeb OS Command Injection (medium 6.7, exploited in the wild)
- [CVE-2020-29015](https://insights.sbomify.com/CVE-2020-29015/): SQL injection in Fortinet FortiWeb (critical 9.8)
- [CVE-2020-29016](https://insights.sbomify.com/CVE-2020-29016/): Memory corruption in Fortinet FortiWeb (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52970 is a high-severity vulnerability in Fortinet Fortiweb, published on 12 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52970 exists.

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

## Sources

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

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