dbcve.org
AutocadApplication · Autodesk

CVE-2025-1430

HIGH · 7.8 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 2022.1.6 / 2023.1.7 or later.
See remediation →
81/100
Remediation priority · High
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 SLDPRT file, when parsed through Autodesk AutoCAD, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to 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 · high confidence

A memory corruption vulnerability exists in Autodesk AutoCAD when parsing maliciously crafted SLDPRT (SolidWorks part) files. The specially crafted file triggers memory corruption during the parsing process, which can be leveraged by an attacker to achieve arbitrary code execution within the context of the current AutoCAD process.

MitigationApply vendor-provided security patches for AutoCAD when available. Until then, avoid opening untrusted or unexpected SLDPRT files from unknown or untrusted sources.

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
AutocadApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad MepApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Civil 3dApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Advance SteelApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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 the installed AutoCAD product
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or check Add/Remove Programs for the exact product name (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel)
    Affected if The product is one of AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel
  2. Determine the installed version number
    In AutoCAD, type VER at the command line and press Enter, or check Help > Product Information to see the full version string (for example: 2024.1.5)
    Affected if The exact version string cannot be determined or is visible in the UI
  3. Compare version against affected ranges
    Match your installed version to these ranges: 2022.x < 2022.1.6; 2023.x < 2023.1.7; 2024.x < 2024.1.7; 2025.x < 2025.1.2. For example, version 2024.1.5 is affected because 5 is less than 7.
    Affected if Your installed version falls within any of these ranges: >= 2022 and < 2022.1.6; >= 2023 and < 2023.1.7; >= 2024 and < 2024.1.7; >= 2025 and < 2025.1.2
  4. Confirm SLDPRT file handling is present
    Attempt to open a legitimate SLDPRT file (SolidWorks part file) in AutoCAD using the OPEN command and selecting SLDPRT as the file type, or check if the file type appears in the Files of Type dropdown
    Affected if AutoCAD can load or preview SLDPRT files, meaning the parsing component is present

You are affected if you have any of the listed AutoCAD products installed AND the version falls within the vulnerable version ranges, since the SLDPRT parsing functionality is included by default in these products.

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 2022.1.6 / 2023.1.7 / 2024.1.7 or later
Fixed in 2022.1.62023.1.72024.1.7
Interim mitigation

Apply vendor-provided security patches for AutoCAD when available. Until then, avoid opening untrusted or unexpected SLDPRT files from unknown or untrusted sources.

Recommended fix High confidence

2022.1.6 (2022), 2023.1.7 (2023), 2024.1.7 (2024), or 2025.1.2 (2025) depending on your release year

  1. Identify the installed Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3d, Civil 3d, or Advance Steel) and its exact version number
  2. Determine which release year (2022, 2023, 2024, or 2025) the installed version belongs to
  3. For AutoCAD 2022 users: Upgrade to version 2022.1.6 or later
  4. For AutoCAD 2023 users: Upgrade to version 2023.1.7 or later
  5. For AutoCAD 2024 users: Upgrade to version 2024.1.7 or later
  6. For AutoCAD 2025 users: Upgrade to version 2025.1.2 or later
  7. Users of AutoCAD Architecture, Electrical, Mechanical, MEP, Plant 3d, Civil 3d, and Advance Steel should apply the corresponding version update (2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2) for their product line
  8. Download the update from the official Autodesk Account portal or use the product's built-in update checker to obtain the patched version
Caveat Minor version updates typically do not introduce breaking changes, but review Autodesk release notes for any compatibility notices or changes to file formats

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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