FortisoarApplication · Fortinet
CVE-2022-35847
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 · uneditedAn improper neutralization of special elements used in a template engine vulnerability [CWE-1336] in FortiSOAR management interface 7.2.0, 7.0.0 through 7.0.3, 6.4.0 through 6.4.4 may allow a remote and authenticated attacker to execute arbitrary code via a crafted payload.
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 confidenceFortiSOAR contains a template injection vulnerability (CWE-1336) in its management interface. An authenticated remote attacker can inject malicious payloads into template engine elements, bypassing sanitization to execute arbitrary code on the underlying system. The vulnerability affects versions 6.4.0-6.4.4, 7.0.0-7.0.3, and 7.2.0.
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
>= 6.4.0, <= 6.4.4>= 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check FortiSOAR versionLog into the FortiSOAR administration console or run the command 'fs-cli --version' or check the About section in the UI to identify the installed version numberAffected if The installed version falls within 6.4.0-6.4.4, 7.0.0-7.0.3, or equals 7.2.0
-
Verify management interface accessibilityConfirm whether the FortiSOAR management interface (typically ports 443 or 8000) is accessible from network segments that contain untrusted usersAffected if The management interface is exposed to untrusted or external networks without proper network segmentation
-
Check for unauthorized template modificationsReview template configurations in the FortiSOAR UI under Playbooks > Templates or examine template files in the /opt/fsr/templates directory for suspicious or unexpected contentAffected if Unexpected template entries, obfuscated code, or payloads containing Jinja2/handlebars syntax are found in template configurations
-
Audit user accounts and login activityReview FortiSOAR audit logs and user authentication records for signs of unauthorized access or anomalous activity targeting the template engineAffected if Unrecognized authenticated sessions exist or unusual commands were executed by accounts with template access privileges
You are affected if FortiSOAR version is 6.4.0-6.4.4, 7.0.0-7.0.3, or 7.2.0 and the management interface is accessible to the attacker.
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 vendor-supplied patches/updates to FortiSOAR to remediate the template injection flaw. Additionally, restrict management interface access to authorized personnel only and implement strong authentication controls to reduce the attack surface.
FortiSOAR 6.4.5 or later; FortiSOAR 7.0.4 or later; FortiSOAR 7.2.1 or later
- 1. Identify the currently installed FortiSOAR version from the FortiSOAR administration panel or via the CLI command: " fwconsole -i | grep Version"
- 2. Based on your current version, plan the upgrade path: If on 6.4.0-6.4.4, upgrade to 6.4.5 or later; If on 7.0.0-7.0.3, upgrade to 7.0.4 or later; If on 7.2.0, upgrade to 7.2.1 or later
- 3. Before upgrading, backup the FortiSOAR database and configuration using the built-in backup feature or CLI: " fwconsole backup"
- 4. Download the appropriate FortiSOAR upgrade package from the Fortinet Customer Support Portal (https://support.fortinet.com)
- 5. Upload and apply the upgrade through the FortiSOAR administration interface under System > Settings > Upgrade, or via CLI using " fwconsole upgrade /path/to/upgrade/package.tar.gz"
- 6. After upgrade completes, verify the new version is installed and confirm the vulnerability is resolved by checking the FortiSOAR version details
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisoar
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35847 — 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-35847 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