FortisoarApplication · Fortinet
CVE-2023-23775
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple improper neutralization of special elements used in SQL commands ('SQL Injection') vulnerabilities [CWE-89] in FortiSOAR 7.2.0 and before 7.0.3 may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted strings parameters.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMultiple SQL injection vulnerabilities in FortiSOAR versions 7.2.0 and before 7.0.3 allow authenticated attackers to execute unauthorized code or commands via specifically crafted string parameters. The vulnerabilities stem from improper neutralization of special elements in SQL commands, affecting multiple parameters throughout the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortisoarApplication
>= 7.0.0, < 7.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the FortiSOAR installed versionLog into the FortiSOAR web interface as an administrator, then navigate to Settings > System > About, or run 'sudo docker ps | grep fortisoar' on the host to identify the container version. Alternatively, check the release notes or the /opt/fsr/etc/VERSION file if accessible.Affected if The installed version is 7.0.0 through 7.2.0, or any version below 7.0.3, specifically versions >= 7.0.0 and < 7.2.1.
-
Verify FortiSOAR web interface accessibilityConfirm whether the FortiSOAR web interface (default ports 8000, 8443, or configured HTTP/HTTPS ports) is accessible from untrusted networks. Check firewall rules and reverse proxy configurations.Affected if The web interface is exposed to the internet or untrusted internal networks without proper network segmentation.
-
Review user authentication logs for SQL injection attemptsAccess FortiSOAR audit logs under Analytics > Dashboards > Audit Logs, or check /var/log/fortisoar/audit.log on the host. Search for SQL-related keywords such as UNION, SELECT, DROP, INSERT, or common injection patterns in API parameters.Affected if Any logs contain suspicious SQL syntax within API request parameters, especially from authenticated user sessions.
-
Check for unauthorized user accounts or privilege escalationNavigate to Administration > Users and Roles > Users in the FortiSOAR interface. Review the user list for accounts that were created or modified without your knowledge, or roles that have been elevated unexpectedly.Affected if Unexpected user accounts exist, or legitimate accounts have been granted elevated privileges they should not have.
You are affected if your FortiSOAR version is 7.0.0 through 7.2.0 (or any version below 7.0.3) and the web interface is accessible to authenticated users, including potentially compromised accounts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.2.1
Upgrade FortiSOAR to version 7.0.3 or later to patch the SQL injection vulnerabilities. Since the attacker requires authentication, also review and restrict user privileges to the minimum necessary.
FortiSOAR 7.2.1
- Download FortiSOAR version 7.2.1 or later from the Fortinet support portal
- Review the FortiSOAR 7.2.1 release notes for any pre-upgrade requirements
- Backup the current FortiSOAR installation and database
- Follow Fortinet's standard upgrade procedure for FortiSOAR (typically via the web UI or CLI using 'execute upgrade' command)
- After upgrade, verify the application is running and all services are operational
- Confirm the SQL injection vulnerability is resolved by testing the previously vulnerable parameter inputs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisoar
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data