FortisoarApplication · Fortinet
CVE-2023-27995
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 · uneditedA improper neutralization of special elements used in a template engine vulnerability in Fortinet FortiSOAR 7.3.0 through 7.3.1 allows an authenticated, remote 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 versions 7.3.0 through 7.3.1 contain a template injection vulnerability allowing authenticated remote attackers to execute arbitrary code via crafted payloads in the template engine. The attacker needs valid credentials to exploit this server-side code execution vulnerability.
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.3.0, < 7.3.2CVSS 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.
-
Identify if FortiSOAR is running in your environmentLook for processes named 'fortisoar', 'cortex-soar', or services listening on ports commonly used by FortiSOAR (default 8000, 8080, or 443). Check your installed applications or infrastructure inventory for FortiSOAR deployments.Affected if FortiSOAR version 7.3.0 or 7.3.1 is installed and running.
-
Determine the installed FortiSOAR versionLog into the FortiSOAR web interface and navigate to the 'System' > 'About' page, or use the CLI command 'frs-admin --version' if you have shell access. Compare the version number against the affected range.Affected if The version is 7.3.0 or 7.3.1.
-
Check if the management interface is network-exposedReview firewall rules and network configurations to determine if the FortiSOAR management interface (ports 443, 8000, 8080) is accessible from untrusted networks such as the public internet or non-corporate segments.Affected if The management interface is exposed to untrusted networks and version is 7.3.0-7.3.1.
-
Verify user account securityReview the list of user accounts in FortiSOAR (Settings > Users > User Management) for any unauthorized or unknown accounts, and check if multi-factor authentication is enabled for all administrative accounts.Affected if Weak or compromised credentials exist and the FortiSOAR version is vulnerable.
-
Review authentication logs for suspicious activityExamine FortiSOAR audit logs (Dashboard > Logs > Audit) for failed login attempts, especially from unusual IP addresses, or successful logins at unusual times, or API activity involving template operations.Affected if Evidence of unauthorized access using valid credentials is found on a vulnerable version.
You are affected if FortiSOAR version 7.3.0 or 7.3.1 is running and the management interface is accessible (even with valid credentials required for exploitation).
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 · scoped7.3.2
Apply the vendor patch by upgrading FortiSOAR to a version beyond 7.3.1. If immediate patching is not possible, restrict network access to the FortiSOAR management interface to trusted IP addresses and review authentication mechanisms.
FortiSOAR 7.3.2
- 1. Verify the current FortiSOAR version by accessing the administration panel or running: open-cli command
- 2. Confirm the version is between 7.3.0 and 7.3.1 (inclusive), which is affected by CVE-2023-27995
- 3. Backup all FortiSOAR configurations and data before proceeding with the upgrade
- 4. Download FortiSOAR version 7.3.2 from the Fortinet customer support portal (fortinet.com/support)
- 5. Apply the upgrade following Fortinet's official upgrade documentation for FortiSOAR 7.3.x
- 6. After upgrade, verify the new version is 7.3.2 using the administration panel
- 7. Confirm the vulnerability is remediated by validating the patch is applied
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-2023-27995 — 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-2023-27995 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