dbcve.org
FusionApplication · Autodesk

CVE-2026-4345

HIGH · 7.1 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 2702.1.47 or later.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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
A maliciously crafted HTML payload, stored in a design name and exported to CSV, can trigger a Stored Cross-site Scripting (XSS) vulnerability in the Autodesk Fusion desktop application. A malicious actor may leverage this vulnerability to read local files or execute arbitrary code in the context of the current process.

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

Stored XSS vulnerability in Autodesk Fusion desktop application where malicious HTML in a design name is exported to CSV, allowing attackers to read local files or execute arbitrary code in the current process context.

MitigationImplement input sanitization and proper output encoding for design names during CSV export, ensuring HTML entities are escaped to prevent script execution.

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
FusionApplication
Affected:< 2702.1.47

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Locate Autodesk Fusion installation
    Check common installation paths: Windows: C:\Program Files\Autodesk\Fusion 360 or %LOCALAPPDATA%\Autodesk\webdeploy\, macOS: /Applications/Autodesk Fusion 360.app. Use 'Get-ItemProperty' or 'ls' to verify existence.
    Affected if Autodesk Fusion is installed on the system
  2. Identify installed Fusion version
    Windows: Run 'Get-ItemProperty "HKLM:\SOFTWARE\Autodesk\Fusion 360" | Select-Object Version' or check Help > About in the application. macOS: Right-click app > Get Info or run 'defaults read /Applications/Autodesk\ Fusion\ 360.app/Contents/Info CFBundleShortVersionString'.
    Affected if Version is lower than 2702.1.47 (e.g., 2702.0.x, earlier stable builds)
  3. Determine if CSV export feature is used
    Review user workflows or recent activity logs for CSV export operations. Check Documents folder or default export locations for .csv files originating from Fusion. Look for files with 'export' or 'csv' in the name or path.
    Affected if Designs have been exported to CSV format at least once
  4. Inspect design names for potential malicious content
    Open Fusion, navigate to the Data Panel or project browser. Examine all design names for unusual characters such as < > " ' or script tags. Check for designs with names containing HTML-like syntax that could indicate past exploitation.
    Affected if Any design name contains unescaped HTML/JavaScript syntax (e.g., <script>, onload=, img src=)

A user is affected if Autodesk Fusion version is below 2702.1.47 AND they have exported designs with potentially malicious design names to CSV, as the XSS payload would be embedded in the exported file.

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 2702.1.47 or later
Fixed in 2702.1.47
Interim mitigation

Implement input sanitization and proper output encoding for design names during CSV export, ensuring HTML entities are escaped to prevent script execution.

Recommended fix Moderate confidence

Fusion version 2702.1.47 or later

  1. Open Autodesk Fusion
  2. Navigate to Help > Check for Updates
  3. If an update is available, download and install version 2702.1.47 or later
  4. Alternatively, download the latest version from the official Autodesk website at www.autodesk.com
  5. Restart the application after updating
  6. Verify the update was successful by checking the version number in Help > About Autodesk Fusion

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

Fix this in Fusion Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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