dbcve.org
FortiaiApplication · Fortinet

CVE-2022-27488

HIGH · 8.8 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to after 7.0.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) in Fortinet FortiVoiceEnterprise version 6.4.x, 6.0.x, FortiSwitch version 7.0.0 through 7.0.4, 6.4.0 through 6.4.10, 6.2.0 through 6.2.7, 6.0.x, FortiMail version 7.0.0 through 7.0.3, 6.4.0 through 6.4.6, 6.2.x, 6.0.x FortiRecorder version 6.4.0 through 6.4.2, 6.0.x, 2.7.x, 2.6.x, FortiNDR version 1.x.x allows a remote unauthenticated attacker to execute commands on the CLI via tricking an authenticated administrator to execute malicious GET 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 confidence

A cross-site request forgery (CSRF) vulnerability in FortiVoiceEnterprise, FortiSwitch, FortiMail, FortiRecorder, and FortiNDR allows remote unauthenticated attackers to execute arbitrary CLI commands by tricking authenticated administrators into clicking malicious GET request links.

MitigationApply vendor-supplemented patches for affected versions; implement anti-CSRF tokens in web interfaces and educate administrators on phishing risks.

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
FortiaiApplication
Affected:= 1.1.0= 1.5.3
FortimailApplication
Affected:>= 6.0.0, <= 6.0.12>= 6.2.0, <= 6.2.9>= 6.4.0, <= 6.4.6>= 7.0.0, <= 7.0.3
FortindrApplication
Affected:>= 7.0.0, <= 7.0.4= 7.1.0
FortirecorderApplication
Affected:>= 2.6.0, <= 2.6.3>= 2.7.0, <= 2.7.7>= 6.0.0, <= 6.0.11>= 6.4.0, <= 6.4.2
FortivoiceApplication
Affected:>= 6.0.0, <= 6.0.11>= 6.4.0, <= 6.4.7
FortiswitchOperating system
Affected:>= 6.0.0, <= 6.0.7>= 6.2.0, <= 6.2.7>= 6.4.0, <= 6.4.10>= 7.0.0, <= 7.0.4

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the Fortinet product running in your environment
    Check system information or login page to determine if you are running FortiMail, FortiVoice, FortiSwitch, FortiRecorder, FortiNDR, or FortiAI. The product name is typically visible on the web login page or in system diagnostics.
    Affected if The product is any of: FortiMail, FortiVoice, FortiSwitch, FortiRecorder, FortiNDR, or FortiAI
  2. Determine the installed version of the Fortinet product
    Access the web administration interface and navigate to System > Settings or use CLI command 'get system status' to retrieve the firmware version. Compare the version number against the affected ranges for your specific product.
    Affected if The installed version falls within any of these ranges: FortiAI: 1.1.0 or 1.5.3; FortiMail: 6.0.0-6.0.12, 6.2.0-6.2.9, 6.4.0-6.4.6, 7.0.0-7.0.3; FortiNDR: 7.0.0-7.0.4 or 7.1.0; FortiRecorder: 2.6.0-2.6.3, 2.7.0-2.7.7, 6.0.0-6.0.11, 6.4.0-6.4.2; FortiVoice: 6.0.0-6.0.11, 6.4.0-6.4.7; FortiSwitch: 6.0
  3. Confirm the web management interface is accessible
    Verify that the HTTP/HTTPS management interface is reachable from network locations where attackers could potentially send malicious links. Check firewall rules and interface bindings.
    Affected if The web interface is exposed to untrusted networks or the internet without proper access restrictions
  4. Verify whether anti-CSRF protections are implemented
    Log into the web interface, perform an action, and examine HTTP requests/responses for anti-CSRF tokens. Check if the Set-Cookie header includes SameSite attributes or if forms contain hidden token fields. Alternatively, capture a legitimate request and attempt to replay it without modifications to see if it succeeds.
    Affected if HTTP requests do not contain unique anti-CSRF tokens and requests can be successfully replayed without authentication tokens

You are affected if your Fortinet product version falls within the affected ranges AND the web management interface is accessible to attackers AND anti-CSRF protections are absent or inadequate.

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 7.0.4
Interim mitigation

Apply vendor-supplemented patches for affected versions; implement anti-CSRF tokens in web interfaces and educate administrators on phishing risks.

Recommended fix Moderate confidence

Upgrade to the latest available version for each product line: FortiVoice (latest 6.4.x or 7.x), FortiSwitch (latest 7.0.x or 7.2.x), FortiMail (latest 7.0.x or 7.4.x), FortiRecorder (latest 6.4.x or 7.x), FortiNDR (latest 7.2.x or newer)

  1. 1. Identify the affected Fortinet product (FortiVoice, FortiSwitch, FortiMail, FortiRecorder, or FortiNDR) and current version from the system dashboard or CLI using 'get system status'.
  2. 2. Determine the product line and current major version (e.g., 6.0.x, 6.2.x, 6.4.x, 7.0.x).
  3. 3. Download the latest available version for that product line from Fortinet's support portal (https://support.fortinet.com).
  4. 4. Review the release notes for the latest version to confirm CSRF fixes are included.
  5. 5. Before upgrading, backup the current configuration using 'execute backup config' via CLI or the web UI.
  6. 6. Plan upgrade during a maintenance window as upgrades may cause brief service interruption.
  7. 7. Upload the firmware file through the web UI under System > Firmware or via CLI using 'execute firmware upgrade'.
  8. 8. After upgrade, verify the system is operational and confirm the new version is installed using 'get system status'.
Caveat Review release notes for each product; major version jumps may introduce configuration or behavioral changes; test in non-production environment first

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

Fix this in Fortiai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27488 — 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-27488 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