dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-9447

HIGH · 7.8 CVSS v3.1 Published 2025-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An Out-Of-Bounds Read vulnerability affecting the PAR file reading procedure in SOLIDWORKS eDrawings on Release SOLIDWORKS Desktop 2025 could allow an attacker to execute arbitrary code while opening a specially crafted PAR file.

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

An Out-Of-Bounds Read vulnerability exists in the PAR file parsing component of SOLIDWORKS eDrawings 2025. When processing a specially crafted PAR file, the application reads memory beyond allocated buffer boundaries, which can be leveraged to achieve arbitrary code execution.

MitigationDo not open untrusted or unverified PAR files in eDrawings. Apply vendor patches from Dassault Systèmes when available. Consider using application whitelisting or sandboxing for eDrawings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Verify eDrawings 2025 installation
    Check for SOLIDWORKS eDrawings 2025 in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look in Program Files for the eDrawings folder
    Affected if eDrawings 2025 is installed on the system
  2. Determine installed eDrawings version
    Right-click the eDrawings executable (typically in C:\Program Files\SOLIDWORKS\eDrawings or similar), select Properties, and note the File Version field
    Affected if The version shows 2025.x.x.x (any 2025 release)
  3. Check PAR file association
    Open Windows Settings > Apps > Default Apps > Choose defaults by file type and look for .par extension, or right-click any .par file and view its 'Opens with' property
    Affected if PAR files are associated with eDrawings or eDrawings can open PAR files
  4. Inspect PAR parsing component
    Examine the eDrawings installation directory for DLLs related to PAR processing (search for files containing 'par' in the filename within the eDrawings bin folder)
    Affected if PAR parsing DLLs are present in the eDrawings installation directory

You are affected if SOLIDWORKS eDrawings version 2025 is installed and PAR file parsing functionality is available on your system.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Do not open untrusted or unverified PAR files in eDrawings. Apply vendor patches from Dassault Systèmes when available. Consider using application whitelisting or sandboxing for eDrawings.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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