Safeguard
Vulnerability Analysis•

CVE-2023-26211: Medium Stored XSS in Fortinet FortiSOAR

CVE-2023-26211 is a medium stored XSS in the FortiSOAR Communications module, 7.3.0 through 7.3.2. Upgrade to 7.3.3 or 7.4.1, or migrate older releases.

Safeguard Security Team
3 min read

CVE-2023-26211 is a medium severity (CVSS 6.8) cross site scripting flaw in the Communications module of Fortinet FortiSOAR. An authenticated remote attacker could inject script. Fortinet says to upgrade 7.3 to 7.3.3 or later and 7.4.0 to 7.4.1 or later.

What's affected

The record says FortiSOAR 7.3.0 through 7.3.2 is affected and its product list also names 7.4.0. Fortinet's advisory FG-IR-23-088 is wider. It lists on premise FortiSOAR 7.4.0 (upgrade to 7.4.1 or above), 7.3.0 through 7.3.2 (upgrade to 7.3.3 or above), and all versions of 7.2, 7.0 and 6.4 (migrate to a fixed release). FortiSOAR 7.5 and 7.6 are listed as not affected.

So the record understates the older branches. If you run 7.2, 7.0 or 6.4, the advisory says they are affected and there is no patch on those lines.

Severity agrees: the advisory shows CVSS 6.8 and a medium rating, with a temporal score of 6.4. Fortinet calls the flaw a stored cross site scripting issue and notes it was discovered internally, with attack type authenticated and known exploited marked as no. The advisory was published on 13 August 2024. The weakness is CWE-79.

How to check if you're exposed

Read the FortiSOAR version from the product's interface or your usual administrative tooling, then compare it against the table above. Fortinet's advisory does not give a command, so I am not guessing one.

Also list who can use the Communications module, because the attack needs an authenticated user with enough rights to write content that others view. The record vector shows high privileges required and user interaction required, so the realistic route is a trusted but misused account.

To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.

What to do now

  1. Check your FortiSOAR version against the advisory table.
  2. Upgrade 7.3.x to 7.3.3 or later, and 7.4.0 to 7.4.1 or later.
  3. Plan a migration to a fixed release if you run 7.2, 7.0 or 6.4.
  4. Review which accounts can write to the Communications module and remove unneeded access.
  5. Search stored communication content for unexpected script markup after the upgrade.

Why it matters

Stored cross site scripting means the application saves attacker supplied content and later shows it to other users without cleaning it. The script then runs in the victim's browser session. In a security orchestration tool, those viewers are analysts, so the session may carry strong rights.

The vector in the record requires high privileges and user interaction, which keeps the score in the medium range. It is still a reason to patch, since an insider or a compromised analyst account could target colleagues. The advisory says it is not known to be exploited, and the record does not flag CISA KEV.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Do older branches get a patch?

No. Fortinet says to migrate 7.2, 7.0 and 6.4 to a fixed release.

Does the record match the advisory?

Mostly. The record names 7.3.0 to 7.3.2 and 7.4.0. The advisory adds that all of 7.2, 7.0 and 6.4 are affected.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.