# CVE-2025-59922: SQL injection in FortiClientEMS

> Authenticated attackers with read-only admin permissions can execute unauthorized SQL commands via crafted HTTP requests in FortiClient EMS.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/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:** 13 Jan 2026
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-229q-96qr-8qq9

## What is CVE-2025-59922?

CVE-2025-59922 is a medium-severity SQL injection vulnerability in Fortinet FortiClientEMS, published on 13 Jan 2026. 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] vulnerability in Fortinet FortiClientEMS 7.4.3 through 7.4.4, FortiClientEMS 7.4.0 through 7.4.1, FortiClientEMS 7.2.0 through 7.2.10, FortiClientEMS 7.0 all versions may allow an authenticated attacker with at least read-only admin permission 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-59922?

It affects 1 product.


Products: Fortinet Forticlientems.

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

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

## Is CVE-2025-59922 being exploited?

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

## Other vulnerabilities in Fortinet FortiClientEMS

- [CVE-2026-35616](https://insights.sbomify.com/CVE-2026-35616/): Fortinet FortiClient EMS Improper Access Control (critical 9.1, exploited in the wild)
- [CVE-2026-21643](https://insights.sbomify.com/CVE-2026-21643/): Fortinet FortiClient EMS SQL Injection (critical 9.1, exploited in the wild)
- [CVE-2024-23106](https://insights.sbomify.com/CVE-2024-23106/): Auth bypass in FortiClientEMS (high 7.7)
- [CVE-2026-59836](https://insights.sbomify.com/CVE-2026-59836/): Security feature bypass in FortiClientEMS (medium 6.7)
- [CVE-2026-39809](https://insights.sbomify.com/CVE-2026-39809/): SQL injection in FortiClientEMS (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59922 is a medium-severity SQL injection vulnerability in Fortinet FortiClientEMS, published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59922 in the wild and no public exploit code.

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

## Sources

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

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