dbcve.org
FortisoarApplication · Fortinet

CVE-2023-26211

CRITICAL · 9.0 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 7.3.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
An improper neutralization of input during web page generation ('cross-site scripting') in Fortinet FortiSOAR 7.3.0 through 7.3.2 allows an authenticated, remote attacker to inject arbitrary web script or HTML via the Communications module.

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 · moderate confidence

This is a stored cross-site scripting (XSS) vulnerability in Fortinet FortiSOAR versions 7.3.0 through 7.3.2. An authenticated attacker can inject malicious JavaScript or HTML payloads through the Communications module, which are then rendered without proper sanitization when other users view the content, potentially allowing session hijacking or credential theft.

MitigationUpgrade FortiSOAR to a version beyond 7.3.2 where the vulnerability has been patched. If immediate patching is not possible, restrict access to the Communications module to trusted users only and implement web application firewall rules to detect and block XSS payloads.

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
Affected:>= 6.4.0, < 7.3.3= 7.4.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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 FortiSOAR is installed
    Check for FortiSOAR service or web interface running on the system, typically on port 8000 or configured port
    Affected if FortiSOAR is not found on the system - not applicable
  2. Determine FortiSOAR version
    Access FortiSOAR CLI and run version command (such as 'exec -v' or 'fortisoar -v') or check via UI under Help > About
    Affected if Version is >= 6.4.0 AND < 7.3.3, or version equals 7.4.0
  3. Check if Communications module is in use
    Review FortiSOAR modules list or check if Communications (email/messaging) records exist in the database
    Affected if Communications module is enabled or has been used to send messages - vulnerability is only exploitable through this module
  4. Audit Communications module content
    Review communications records or email logs stored in FortiSOAR database for any unexpected script tags or HTML in message content fields
    Affected if Malicious JavaScript/HTML code is found embedded in communication records

User is affected if FortiSOAR version falls within 6.4.0 to 7.3.2 or equals 7.4.0 AND the Communications module is in use, as this is the attack vector for the stored XSS

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 7.3.3 or later
Fixed in 7.3.3
Interim mitigation

Upgrade FortiSOAR to a version beyond 7.3.2 where the vulnerability has been patched. If immediate patching is not possible, restrict access to the Communications module to trusted users only and implement web application firewall rules to detect and block XSS payloads.

Recommended fix High confidence

FortiSOAR 7.3.3 or later (recommended: latest stable 7.x release)

  1. 1. Identify the current FortiSOAR version by navigating to the admin settings or using the command line interface.
  2. 2. Confirm the current version is within the affected range: 6.4.0 through 7.3.2, or version 7.4.0.
  3. 3. Plan the upgrade during a maintenance window to minimize business impact.
  4. 4. Backup the FortiSOAR database and configuration before proceeding with the upgrade.
  5. 5. Download FortiSOAR version 7.3.3 or later from the Fortinet support portal (support.fortinet.com).
  6. 6. Follow Fortinet's official upgrade documentation to apply the upgrade package.
  7. 7. After upgrade completion, verify the Communications module is functioning correctly.
  8. 8. Validate the fix by confirming the XSS vulnerability is no longer present in the Communications module.
Caveat Review FortiSOAR release notes for version 7.3.3 for any configuration or compatibility changes before upgrading

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
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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