dbcve.org
FusionApplication · Autodesk

CVE-2025-10244

HIGH · 8.7 CVSS v3.1 Published 2025-09-23
Fix available
A fix is available. Upgrade to 2604.1.25 or later.
See remediation →
91/100
Remediation priority · Urgent
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
A maliciously crafted HTML payload, when rendered by the Autodesk Fusion desktop application, can trigger a Stored Cross-site Scripting (XSS) vulnerability. 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 Cross-site Scripting (XSS) vulnerability exists in the Autodesk Fusion desktop application where maliciously crafted HTML payloads are not properly sanitized before rendering. When a user opens a project file or data containing the malicious payload, the embedded JavaScript executes within the application's context, enabling local file system access and arbitrary code execution on the affected machine.

MitigationImplement strict HTML sanitization using a robust library (e.g., DOMPurify) for all user-supplied content before rendering, and apply Content Security Policy headers to restrict script execution. Users should avoid opening untrusted project files until a patch is applied.

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:>= 2602.1.25, < 2604.1.25

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Verify Autodesk Fusion installation exists
    Check for Autodesk Fusion 360 installation directory (typically C:\Program Files\Autodesk\Fusion 360) or look for the application in Add/Remove Programs on Windows, orApplications folder on macOS
    Affected if Autodesk Fusion is installed on the machine
  2. Locate the installed Fusion version number
    Open Fusion, go to Help > About Autodesk Fusion 360, or check the version in the application's executable properties, or look in the Windows Registry under HKLM\SOFTWARE\Autodesk\Fusion 360 for the Version value
    Affected if Version number cannot be determined
  3. Compare installed version against affected range
    Take the identified version (e.g., 2602.1.25 or 2603.0.0) and verify it falls within >= 2602.1.25 AND < 2604.1.25
    Affected if Installed version is 2602.1.25 or later but earlier than 2604.1.25
  4. Assess exposure to untrusted project files
    Determine whether the user or team routinely opens project files (.f3d, .f3z, or other Fusion file formats) from external or untrusted sources, or receives them via email or download
    Affected if User opens project files from untrusted or external sources

User is affected if Autodesk Fusion is installed with a version between 2602.1.25 and 2604.1.25 (inclusive of lower bound, exclusive of upper bound) and they open untrusted project files.

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

Implement strict HTML sanitization using a robust library (e.g., DOMPurify) for all user-supplied content before rendering, and apply Content Security Policy headers to restrict script execution. Users should avoid opening untrusted project files until a patch is applied.

Recommended fix High confidence

2604.1.25 or later

  1. Check current Autodesk Fusion version by going to Help > About Fusion
  2. If version is >= 2602.1.25 and < 2604.1.25, the installation is vulnerable
  3. Upgrade to version 2604.1.25 or later through the application's built-in update mechanism (Help > Check for Updates)
  4. Alternatively, download the latest version from Autodesk's official website at www.autodesk.com
  5. After upgrading, verify the new version by checking Help > About Fusion

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

Fix this in Fusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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