dbcve.org
FusionApplication · Autodesk

CVE-2026-4344

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 in a component name, when displayed during the delete confirmation dialog and clicked by a user, 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

A stored XSS vulnerability exists in Autodesk Fusion's delete confirmation dialog where malicious HTML/JavaScript embedded in a component name persists in the application and executes when a user clicks the displayed name during confirmation. This allows attackers to potentially read local files or execute arbitrary code within the application's process context.

MitigationImplement strict input validation and context-aware output encoding for all component names at storage and display time, combined with Content Security Policy headers to restrict 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. Identify installed Autodesk Fusion version
    Open Autodesk Fusion, then navigate to Help > About Autodesk Fusion (or check the application properties in the system). Record the exact version number displayed.
    Affected if The reported version is less than 2702.1.47 (for example, 2702.1.46, 2702.0.x, or earlier).
  2. Verify delete confirmation dialog functionality exists
    In Autodesk Fusion, create a component, then attempt to delete it. Observe if a delete confirmation dialog appears displaying the component name before deletion.
    Affected if The delete confirmation dialog appears and shows the component name being deleted.
  3. Inspect component name storage in project data
    Locate the project folder for your Fusion design. Examine any JSON, XML, or database files that store component metadata for component names stored in the project.
    Affected if Component names are stored in plain text without visible sanitization markers (the application relies on output encoding at display time only).
  4. Check for evidence of prior exploitation
    Search project files for suspicious patterns in component names such as <script>, javascript:, onload=, onerror=, or iframe tags embedded within component name fields.
    Affected if Any component name field contains HTML tags or JavaScript event handlers (for example, <img src=x onerror=alert(1)>).

You are affected if your Autodesk Fusion version is below 2702.1.47 and you use the delete confirmation dialog feature, especially if unsanitized content is found in component names.

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 strict input validation and context-aware output encoding for all component names at storage and display time, combined with Content Security Policy headers to restrict script execution.

Recommended fix Moderate confidence

Fusion version 2702.1.47 or later

  1. 1. Open Autodesk Fusion on your desktop application
  2. 2. Navigate to the Help menu or Settings
  3. 3. Check the current version number under 'About Autodesk Fusion' or 'Version Info'
  4. 4. If version is below 2702.1.47, download the latest update from the official Autodesk website or use the built-in update checker
  5. 5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. 6. After upgrading, verify the version shows 2702.1.47 or higher

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

Fix this in Fusion Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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