CVE-2023-23775 is a medium severity SQL injection flaw (CVSS 6.5) in Fortinet FortiSOAR. An authenticated attacker can use specially crafted string parameters to run unauthorized commands against the database. Fortinet documents the affected and fixed releases in advisory FG-IR-22-448, so check your version there and upgrade.
What's affected
- Fortinet FortiSOAR. The record gives the range as "7.2.0 and before 7.0.3", which is unusual wording.
- The record does not name a fixed version outside that phrase. Fortinet advisory FG-IR-22-448 is the authority.
- Attack requirements: network access and a low privilege account, no user interaction.
- Severity: CVSS 3.1 score 6.5 Medium, vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. Confidentiality is the only impact.
Fortinet's PSIRT page returned an unavailable notice when we fetched it, so we could not confirm which branches are affected or fixed. The phrase in the record can be read in more than one way. Do not rely on it. Open FG-IR-22-448 and match your exact FortiSOAR build.
How to check if you're exposed
FortiSOAR shows its version in the web interface, usually in the system or about section of the administration pages. You can also read it from the appliance command line if you have access, using the version command the Fortinet documentation lists for your release.
Write down the full build number, since the advisory is specific about branches. Then compare it with the affected and fixed ranges in FG-IR-22-448.
What to do now
- Identify every FortiSOAR instance and its full version and build.
- Read FG-IR-22-448 and match your branch to the fixed release.
- Upgrade to the fixed release, or to a later supported one, following Fortinet's upgrade guidance.
- Review which accounts can sign in. The attacker needs a low privilege account, so trim unused ones.
- Check database and application logs for unusual queries or data export activity.
Why it matters
The weakness is SQL injection (CWE-89 (SQL Injection)). The application builds a database query using input from a user without neutralizing special characters. The database then treats part of that input as instructions instead of data. Fortinet describes the possible result as unauthorized code or commands.
A SOAR platform sits close to sensitive material, including alerts, case notes and credentials for connected tools. The record shows high confidentiality impact and no integrity or availability impact, so the main concern is data being read. The attack needs an account, which narrows who can try it but does not remove the risk. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why not just trust the version range in the record?
Because the wording is ambiguous, and we could not load the Fortinet page to settle it. The advisory is the only source that names exact builds.
Does the attacker need an account?
Yes. The vector shows a low privilege account is required.
Sources
Last reviewed: 19 October 2026.