dbcve.org
AutocadApplication · Autodesk

CVE-2023-27913

HIGH · 7.8 CVSS v3.1 Published 2023-04-14
Fix available
A fix is available. Upgrade to 2023.1.3 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 X_B file when parsed through Autodesk® AutoCAD® 2023 can be used to cause an Integer Overflow. A malicious actor can leverage this vulnerability to cause a crash or read sensitive data, 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 vulnerability in AutoCAD 2023 allows parsing of a maliciously crafted X_B file to trigger an integer overflow, which can cause a crash, enable sensitive data disclosure, or allow arbitrary code execution in the current process context.

MitigationApply the vendor patch or update to a fixed version of AutoCAD 2023 when released; avoid opening X_B files from 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:>= 2023, < 2023.1.3
Autocad Advance SteelApplication
Affected:>= 2023, < 2023.1.3
Autocad ArchitectureApplication
Affected:>= 2023, < 2023.1.3
Autocad Civil 3dApplication
Affected:>= 2023, < 2023.1.3
Autocad ElectricalApplication
Affected:>= 2023, < 2023.1.3
Autocad LtApplication
Affected:>= 2023, < 2023.1.3
Autocad Map 3dApplication
Affected:>= 2023, < 2023.1.3
Autocad MechanicalApplication
Affected:>= 2023, < 2023.1.3

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 installed AutoCAD product variant
    Open AutoCAD and go to Help > About AutoCAD, or check Add/Remove Programs in Windows Control Panel to see which AutoCAD 2023 product is installed
    Affected if Any of the following products are installed: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3d, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3d, or AutoCAD Mechanical
  2. Determine the installed version number
    In AutoCAD, type 'VER' or 'ABOUT' at the command line, or check the version in Help > About AutoCAD. Note the full version string (for example, the build number)
    Affected if The version is 2023 but earlier than 2023.1.3 (or the build number falls below the 2023.1.3 threshold)
  3. Confirm X_B file import capability
    X_B files are a DXF exchange format; the vulnerability triggers when AutoCAD attempts to parse this file type. Verify the product includes the standard DXF/DWG import handlers by attempting to import an X_B file or checking file import options under Insert > Import
    Affected if X_B file import is available and the version check in step 2 shows an affected version

You are affected if any AutoCAD 2023 product variant (including Advance Steel, Architecture, Civil 3d, Electrical, LT, Map 3d, or Mechanical) is installed with a version earlier than 2023.1.3 and the X_B file import feature is functional.

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

Apply the vendor patch or update to a fixed version of AutoCAD 2023 when released; avoid opening X_B files from untrusted sources.

Recommended fix High confidence

2023.1.3 or later

  1. Verify current installed version of AutoCAD product (Help > About AutoCAD > Product Information)
  2. Ensure all active drawings and custom settings are backed up to a secure location
  3. Uninstall any previous updates or service packs for the current installation
  4. Download AutoCAD 2023.1.3 (or later) update from the official Autodesk website (www.autodesk.com) or your Autodesk Account
  5. Run the installer with administrator privileges
  6. Follow the on-screen installation prompts, selecting 'Upgrade' or 'Repair' as appropriate
  7. Restart the application after installation completes
  8. Verify the installed version shows 2023.1.3 or later (Help > About AutoCAD > Product Information)
Caveat Minor version upgrade within same major release; standard backup recommended before any software update

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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