dbcve.org
FortisoarApplication · Fortinet

CVE-2024-47572

HIGH · 8.0 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.3.3 / 7.4.2 or later.
See remediation →
84/100
Remediation priority · High
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 formula elements in a csv file in Fortinet FortiSOAR 7.2.1 through 7.4.1 allows attacker to execute unauthorized code or commands via manipulating csv file

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 confidence

FortiSOAR 7.2.1 through 7.4.1 contains a CSV injection vulnerability where the application fails to properly neutralize formula elements (characters like =, +, -, @) within imported CSV files. When users open manipulated CSV files, the embedded spreadsheet formulas can execute arbitrary commands on the victim's machine via DDE attacks or similar spreadsheet formula execution vectors.

MitigationImplement input validation to strip or neutralize formula-initiating characters (=, +, -, @, tab) from CSV field values during import, and use safe parsing libraries that treat all content as literal text rather than evaluable formulas.

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.2.1, <= 7.2.2>= 7.3.0, < 7.3.3>= 7.4.0, < 7.4.2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiSOAR installed version
    Log into the FortiSOAR web interface and navigate to the About or System Settings page to view the current version number, or use the CLI command 'system version' if available
    Affected if The installed version falls within 7.2.1 through 7.2.2, 7.3.0 through 7.3.2, or 7.4.0 through 7.4.1 (any version >= 7.2.1 and < 7.2.3, >= 7.3.0 and < 7.3.3, or >= 7.4.0 and < 7.4.2)
  2. Confirm CSV import functionality is accessible
    Verify whether the CSV import feature is available in your FortiSOAR environment by checking the Playbooks, Templates, or Data Ingestion sections where CSV files can be uploaded
    Affected if CSV import functionality exists and users have permissions to import CSV files into the system
  3. Review import processing configuration
    Inspect the system configuration or data ingestion settings to determine how imported CSV files are processed and whether any input validation is applied to the file contents
    Affected if CSV import processing allows raw field values to be passed through without sanitizing formula-initiating characters (=, +, -, @, tab)
  4. Check for custom input validation rules
    Look for any custom validation or enrichment playbooks that may process CSV data upon import, and examine whether these handle special characters in field values
    Affected if No custom validation rules exist that strip or neutralize formula characters from CSV field values during import

Your environment is affected if FortiSOAR version is within the ranges specified and the CSV import feature is used, as the application does not neutralize formula characters in imported CSV files by default.

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.3.3 / 7.4.2 or later
Fixed in 7.3.37.4.2
Interim mitigation

Implement input validation to strip or neutralize formula-initiating characters (=, +, -, @, tab) from CSV field values during import, and use safe parsing libraries that treat all content as literal text rather than evaluable formulas.

Recommended fix Moderate confidence

FortiSOAR 7.2.3 or later (7.2.x branch), 7.3.3 or later (7.3.x branch), or 7.4.2 or later (7.4.x branch)

  1. 1. Identify the current FortiSOAR version by checking the UI (Help > About) or using the 'csadm --version' command
  2. 2. Determine the appropriate upgrade path based on your current version: for 7.2.x go to 7.2.3+, for 7.3.x go to 7.3.3+, for 7.4.x go to 7.4.2+
  3. 3. Back up the FortiSOAR database and configuration before upgrading
  4. 4. Download the appropriate FortiSOAR upgrade package from Fortinet Customer Support portal (https://support.fortinet.com)
  5. 5. Follow Fortinet's standard upgrade procedure for FortiSOAR: upload the upgrade file via the UI (Settings > System > Maintenance > Firmware) or use the command line
  6. 6. After upgrade, verify the version matches the target fixed release
  7. 7. Test CSV import functionality to confirm the fix is working
Caveat Standard FortiSOAR upgrade considerations apply: review release notes for any configuration or feature changes between versions

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 / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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