# CVE-2025-25257: Fortinet FortiWeb SQL Injection

> Unauthenticated attackers can execute unauthorized SQL commands via crafted HTTP requests in FortiWeb, potentially compromising data integrity and confidentiality.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:C`)
- **Exploited in the wild:** Yes, since 18 Jul 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-mj4r-rpwm-gg33

## What is CVE-2025-25257?

CVE-2025-25257 is a critical SQL injection vulnerability in Fortinet Fortiweb, published on 17 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability [CWE-89] vulnerability in Fortinet FortiWeb 7.6.0 through 7.6.3, FortiWeb 7.4.0 through 7.4.7, FortiWeb 7.2.0 through 7.2.10, FortiWeb 7.0.0 through 7.0.10 allows an unauthenticated attacker to execute unauthorized SQL code or commands via crafted HTTP or HTTPs requests.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Fortinet Fortiweb.

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

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

## Is CVE-2025-25257 being exploited?

Yes. Attackers have exploited CVE-2025-25257 in the wild since at least 18 Jul 2025.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-FortiWeb-CVE-2025-25257 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-FortiWeb-CVE-2025-25257
- FortiWeb CVE-2025-25257 exploit (github_poc): https://github.com/0xbigshaq/CVE-2025-25257
- Public PoC for CVE-2025-25257: FortiWeb pre-auth SQLi to RCE (github_poc): https://github.com/TheStingR/CVE-2025-25257
- PoC for CVE-2025-25257, a critical unauthenticated SQL injection in FortiWeb. Exploits SQLi via the Authorization header to write a webshell and gain RCE. No login required. Fully automated. (github_poc): https://github.com/0xgh057r3c0n/CVE-2025-25257
- Exploiting the CVE-2025-25257 vulnerability in FortiWeb. This repository demonstrates secure pre-authenticated SQL injection. (github_poc): https://github.com/aitorfirm/CVE-2025-25257
- https://github.com/imbas007/CVE-2025-25257 (github_poc): https://github.com/imbas007/CVE-2025-25257

## Other vulnerabilities in Fortinet Fortiweb

- [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)
- [CVE-2021-42756](https://insights.sbomify.com/CVE-2021-42756/): Memory corruption in FortiWeb (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25257 is a critical SQL injection vulnerability in Fortinet Fortiweb, published on 17 Jul 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-25257 in the wild since at least 18 Jul 2025.

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

## Sources

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

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