FortisoarApplication · Fortinet
CVE-2022-38379
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 · uneditedImproper neutralization of input during web page generation [CWE-79] in FortiSOAR 7.0.0 through 7.0.3 and 7.2.0 may allow an authenticated attacker to inject HTML tags via input fields of various components within FortiSOAR.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability (CWE-79) in FortiSOAR versions 7.0.0-7.0.3 and 7.2.0. An authenticated attacker can inject malicious HTML tags through input fields in various components, which are then rendered without proper sanitization, allowing script execution in the context of other users' browsers.
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
>= 7.0.0, <= 7.0.3= 7.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiSOAR installed versionLog into the FortiSOAR web interface and navigate to the System Settings or About section to view the product version. Alternatively, use the API endpoint /api/ioc/actor/system/info or check the configuration file that stores version information.Affected if Version cannot be determined or is not visible
-
Confirm version is within affected rangeCompare the installed version against the affected ranges: 7.0.0 through 7.0.3, or exactly version 7.2.0. Note that versions outside this range (below 7.0.0, between 7.0.4-7.1.x, or above 7.2.0) are not affected by this CVE.Affected if Installed version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.2.0
-
Verify authentication requirementConfirm that the FortiSOAR instance requires user authentication. This vulnerability requires an authenticated attacker to inject malicious script through input fields.Affected if FortiSOAR is publicly accessible without authentication controls
The environment is affected if FortiSOAR version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.2.0 and the application accepts user input through web interfaces that are rendered without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch for FortiSOAR 7.0.3/7.2.0 or upgrade to a patched version. Additionally, implement input validation and output encoding for all user-supplied data rendered in web pages.
FortiSOAR 7.2.2 or later (or FortiSOAR 7.0.4 or later if staying on 7.0.x branch)
- 1. Review the FortiSOAR release notes for version 7.2.2 or later to confirm the security fix for CVE-2022-38379 is included
- 2. Create a backup of the current FortiSOAR configuration and database
- 3. Schedule a maintenance window for the upgrade
- 4. Download the FortiSOAR 7.2.2 (or latest stable) upgrade package from the Fortinet Customer Support Portal
- 5. Follow Fortinet's standard upgrade procedure for FortiSOAR - typically via the UI (Setup > Settings > System > Firmware) or CLI
- 6. After upgrade, verify the system is operational and all services are running
- 7. Test that the previously vulnerable input fields now properly sanitize HTML tags
- 8. Confirm the FortiSOAR version reflects the upgrade (Admin > Settings > About)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisoar
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38379 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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