dbcve.org
FortinacApplication · Fortinet

CVE-2022-26116

HIGH · 8.8 CVSS v3.1 Published 2022-05-11
Fix available
A fix is available. Upgrade to after 9.2.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Multiple improper neutralization of special elements used in SQL commands ('SQL Injection') vulnerability [CWE-89] in FortiNAC version 8.3.7 and below, 8.5.2 and below, 8.5.4, 8.6.0, 8.6.5 and below, 8.7.6 and below, 8.8.11 and below, 9.1.5 and below, 9.2.2 and below 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 confidence

SQL injection vulnerability in FortiNAC allows authenticated attackers to execute unauthorized code or commands through specially crafted string parameters due to improper neutralization of SQL special elements (CWE-89).

MitigationApply vendor-supplied patches for affected FortiNAC versions (upgrade to 8.4.0, 8.5.3, 8.5.5, 8.6.1, 8.6.6, 8.7.7, 8.9.0, 9.1.6, 9.3.0, or later per Fortinet advisory) to remediate the SQL injection vulnerability.

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
FortinacApplication
Affected:<= 8.3.7>= 8.5.0, <= 8.5.2>= 8.6.2, <= 8.6.5>= 8.7.0, <= 8.7.6>= 8.8.0, <= 8.8.11>= 9.1.0, <= 9.1.5>= 9.2.0, <= 9.2.2= 8.5.4= 8.6.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if FortiNAC is deployed in your environment
    Check for FortiNAC processes or services running on the system. Typical FortiNAC management ports are 8443 (HTTPS management) and 4567 (portal). On the system, look for processes named 'fnac', 'breezecom', or check the /opt/ folder for FortiNAC installation directories.
    Affected if FortiNAC software is installed and running in your environment.
  2. Determine the installed FortiNAC version
    Log into the FortiNAC web interface and check the version displayed in the footer of any page. Alternatively, access the CLI and run the command 'fnac -v' or 'get system status' to retrieve the firmware version.
    Affected if You can retrieve a FortiNAC version number.
  3. Compare your version against affected ranges
    Reference the version obtained in the previous step and compare it against ALL of these affected ranges: versions <= 8.3.7, >= 8.5.0 through 8.5.2, = 8.5.4, = 8.6.0, >= 8.6.2 through 8.6.5, >= 8.7.0 through 8.7.6, >= 8.8.0 through 8.8.11, >= 9.1.0 through 9.1.5, and >= 9.2.0 through 9.2.2.
    Affected if Your installed version matches any of the affected ranges listed above.
  4. Verify if the management interface is accessible
    Confirm whether the FortiNAC administrative web interface (typically on port 8443) or CLI is accessible from your network. This is the attack surface where the SQL injection payload would be delivered.
    Affected if The FortiNAC management interface or API is reachable on the network.

Your environment is affected if FortiNAC is running and its version matches any of the listed affected ranges AND the management interface is network-accessible, since the SQL injection requires an authenticated attacker to send specially crafted requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 9.2.2
Interim mitigation

Apply vendor-supplied patches for affected FortiNAC versions (upgrade to 8.4.0, 8.5.3, 8.5.5, 8.6.1, 8.6.6, 8.7.7, 8.9.0, 9.1.6, 9.3.0, or later per Fortinet advisory) to remediate the SQL injection vulnerability.

Recommended fix Moderate confidence

FortiNAC version 9.2.3 or later (or the latest available version per Fortinet's release schedule)

  1. Identify the current FortiNAC version running in your environment using the FortiNAC CLI or web UI
  2. Navigate to the Fortinet support portal at https://support.fortinet.com/ and download the latest FortiNAC version for your hardware/virtual appliance model
  3. Review FortiNAC upgrade documentation and release notes for your current version to understand the upgrade path
  4. Schedule a maintenance window as upgrades may require system downtime
  5. Back up the FortiNAC configuration before initiating the upgrade
  6. Follow the documented upgrade procedure for your specific FortiNAC deployment type (physical appliance, VM, or container)
  7. After upgrade, verify the new version is running and confirm all services are operational
  8. Validate that the SQL injection vulnerability is resolved by reviewing the release notes of the applied version
Caveat Review release notes for your specific upgrade path - some major version upgrades may require additional migration steps or have compatibility considerations with connected systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortinac Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26116 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26116 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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