FortiadcApplication · Fortinet
CVE-2022-26120
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 an SQL Command ('SQL Injection') vulnerabilities [CWE-89] in FortiADC management interface 7.0.0 through 7.0.1, 5.0.0 through 6.2.2 may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests.
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 confidenceSQL injection vulnerabilities in FortiADC management interface versions 7.0.0-7.0.1 and 5.0.0-6.2.2 allow authenticated attackers to execute unauthorized code or commands via specifically crafted HTTP requests due to improper neutralization of special elements in SQL commands.
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
FortiadcApplication
>= 5.0.0, < 6.2.3= 7.0.0= 7.0.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 FortiADC installationLocate FortiADC appliances or virtual instances in your environment. This may be a physical appliance, virtual machine, or container running FortiADC software.Affected if FortiADC is deployed in your environment and the management interface is accessible.
-
Determine FortiADC versionAccess the management interface and navigate to the System > Firmware or Dashboard page to view the current firmware version. Alternatively, use the CLI command 'get system status' to retrieve the version information.Affected if The installed version falls within 5.0.0 to 6.2.2, or is exactly 7.0.0 or 7.0.1.
-
Verify management interface accessibilityConfirm that the FortiADC management interface (HTTP/HTTPS on ports 80/443 or custom management ports) is reachable from network segments. Check firewall rules and interface bindings.Affected if The management interface is exposed to network segments where untrusted users could potentially authenticate.
-
Review admin account configurationCheck the list of administrative users configured in FortiADC via the management interface under User > User Group or via CLI command 'get admin user'. Verify which users have SQL injection-prone privileges.Affected if Administrative accounts exist that could be leveraged by an authenticated attacker to exploit the SQL injection.
You are affected if FortiADC is running version 5.0.0 through 6.2.2 or versions 7.0.0-7.0.1, the management interface is accessible to authenticated users, and an attacker with admin credentials could submit crafted HTTP requests.
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 · scoped6.2.3
Upgrade FortiADC to version 7.0.2 or later (for 7.x) and 6.2.3 or later (for 5.x/6.x). If immediate patching is not possible, restrict access to the management interface to trusted networks only and implement additional authentication controls.
FortiADC 5.x-6.2.x: upgrade to >= 6.2.3; FortiADC 7.0.0-7.0.1: upgrade to >= 7.0.2 (recommended: latest stable 7.2.x)
- 1. Identify the current FortiADC firmware version by navigating to FortiADC UI > Dashboard > System Information widget or running 'get system status' via CLI.
- 2. For FortiADC 5.x-6.2.x versions: Plan an upgrade to version 6.2.3 or later (recommended: latest 6.2.x stable release).
- 3. For FortiADC 7.0.0 or 7.0.1: Plan an upgrade to version 7.0.2 or later (recommended: latest 7.0.x stable release or upgrade to 7.1.x/7.2.x).
- 4. Before upgrading, back up the current configuration via CLI: 'execute backup config tftp <config-name> <tftp-server-ip>' or via UI: System > Maintenance > Backup & Restore.
- 5. Review FortiADC upgrade path documentation to ensure compatibility with your deployment topology.
- 6. Upload the new firmware image via FortiADC UI: System > Firmware > Upload or via CLI: 'execute upload image <image-file>'.
- 7. After upload, install the firmware and reboot: 'execute reboot' or via the UI upgrade process.
- 8. Verify the system comes up normally and confirm the new version: 'get system status'.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiadc
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26120 — 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-2022-26120 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