dbcve.org
FortisoarApplication · Fortinet

CVE-2026-22154

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 7.5.3 / 7.6.4 or later.
See remediation →
58/100
Remediation priority · Elevated
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') vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.3, FortiSOAR PaaS 7.5.0 through 7.5.2, FortiSOAR PaaS 7.4 all versions, FortiSOAR PaaS 7.3 all versions, FortiSOAR on-premise 7.6.0 through 7.6.3, FortiSOAR on-premise 7.5.0 through 7.5.2, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow an authenticated remote attacker to perform a stored cross site scripting (XSS) attack via 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability in Fortinet FortiSOAR allows authenticated remote attackers to inject malicious scripts via crafted HTTP requests. The malicious payload is stored and executed when other authenticated users view the affected content in the web interface.

MitigationApply the vendor-supplied patch for FortiSOAR versions 7.3 through 7.6.3. Until patched, restrict user privileges for HTTP request handling and implement strict input validation with output encoding on all user-supplied content.

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:>= 7.3.0, < 7.5.3>= 7.6.0, < 7.6.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Check FortiSOAR version via CLI
    Log into the FortiSOAR CLI and run the command `execute system version` or `fortisoar --version` to retrieve the installed version number.
    Affected if The displayed version falls within >= 7.3.0 and < 7.5.3, or >= 7.6.0 and < 7.6.4.
  2. Check FortiSOAR version via web UI
    Log into the FortiSOAR web interface, navigate to Help > About or System Settings > General, and locate the version information displayed there.
    Affected if The displayed version falls within the affected ranges specified above.
  3. Compare version against advisory ranges
    Document the exact version number (for example, 7.4.2 or 7.6.1) and manually compare it to the affected ranges: 7.3.0 <= version < 7.5.3 OR 7.6.0 <= version < 7.6.4.
    Affected if Your installed version matches any of the affected ranges.
  4. Identify content modules accepting user input
    Review which FortiSOAR modules (such as alerts, incidents, playbooks, or custom connectors) accept and store user-supplied content that gets rendered in the web interface for other users.
    Affected if The system stores and displays user-generated content to other authenticated users without strict output encoding.

You are affected if your FortiSOAR version is 7.3.0 or higher but lower than 7.5.3, or 7.6.0 or higher but lower than 7.6.4.

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.5.3 / 7.6.4 or later
Fixed in 7.5.37.6.4
Interim mitigation

Apply the vendor-supplied patch for FortiSOAR versions 7.3 through 7.6.3. Until patched, restrict user privileges for HTTP request handling and implement strict input validation with output encoding on all user-supplied content.

Recommended fix Moderate confidence

FortiSOAR 7.5.3+ or 7.6.4+ (depending on your current branch)

  1. 1. Identify your current FortiSOAR version by navigating to the UI dashboard or checking system information.
  2. 2. For FortiSOAR 7.5.x installations: Upgrade to version 7.5.3 or later.
  3. 3. For FortiSOAR 7.6.x installations: Upgrade to version 7.6.4 or later.
  4. 4. For FortiSOAR 7.3.x and 7.4.x installations: Upgrade to the minimum fixed release in your respective branch (7.5.3 or later for 7.5 branch, 7.6.4 or later for 7.6 branch).
  5. 5. After upgrade, verify the system is functioning correctly and test that the XSS vulnerability is remediated.
  6. 6. Review FortiSOAR release notes for any known issues or additional prerequisites before upgrading.
Caveat Review release notes for version-specific changes; test in non-production environment first

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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