# CVE-2025-24474: SQL injection in FortiAnalyzer

> An authenticated high-privilege attacker can extract database information from FortiManager and FortiAnalyzer via SQL injection in crafted requests.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-h86m-jj8c-794w

## What is CVE-2025-24474?

CVE-2025-24474 is a low-severity SQL injection vulnerability in Fortinet Fortianalyzer, published on 8 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability [CWE-89] in FortiManager 7.6.0 through 7.6.1, 7.4.0 through 7.4.6, 7.2 all versions, 7.0 all versions, 6.4 all versions; FortiManager Cloud 7.4.1 through 7.4.6, 7.2 all versions, 7.0 all versions, 6.4 all versions; FortiAnalyzer 7.6.0 through 7.6.1, 7.4.0 through 7.4.6, 7.2 all versions, 7.0 all versions, 6.4 all versions; and FortiAnalyzer Cloud 7.4.1 through 7.4.6, 7.2 all versions, 7.0 all versions, 6.4 all versions may allow an authenticated attacker with high privilege to extract database information via crafted requests.

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

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

It affects 4 products.


Products: Fortinet Fortianalyzer, Fortinet Fortianalyzer Cloud, Fortinet Fortimanager, Fortinet Fortimanager Cloud.

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

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

## Is CVE-2025-24474 being exploited?

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

## Other vulnerabilities in Fortinet Fortianalyzer

- [CVE-2026-24858](https://insights.sbomify.com/CVE-2026-24858/): Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel (critical 9.4, exploited in the wild)
- [CVE-2023-25610](https://insights.sbomify.com/CVE-2023-25610/): Memory corruption in FortiAnalyzer (critical 9.3)
- [CVE-2021-32603](https://insights.sbomify.com/CVE-2021-32603/): Server-side request forgery in Fortinet FortiAnalyzer, FortiManager (high 8.8)
- [CVE-2020-12817](https://insights.sbomify.com/CVE-2020-12817/): Cross-site scripting in Fortinet FortiAnalyzer (high 8.8)
- [CVE-2024-48886](https://insights.sbomify.com/CVE-2024-48886/): Auth bypass in FortiOS (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24474 is a low-severity SQL injection vulnerability in Fortinet Fortianalyzer, published on 8 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24474 in the wild and no public exploit code.

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

## Sources

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

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