dbcve.org
Use After FreeWeakness · CWE-416

CVE-2025-1884

HIGH · 7.8 CVSS v3.1 Published 2025-05-02
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
Use-After-Free vulnerability exists in the SLDPRT file reading procedure in SOLIDWORKS eDrawings on Release SOLIDWORKS Desktop 2025. This vulnerability could allow an attacker to execute arbitrary code while opening a specially crafted SLDPRT 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

A use-after-free vulnerability exists in eDrawings 2025's SLDPRT file parser. When processing a specially crafted SLDPRT file, the application frees a memory object but later attempts to access it after freeing, leading to arbitrary code execution via controlled memory corruption.

MitigationApply the vendor patch from SOLIDWORKS when released. Until then, instruct users to avoid opening SLDPRT files from untrusted sources and consider disabling eDrawings file associations or running the application in a sandbox.

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 is installed
    Check for eDrawings installation directory (typically C:\Program Files\SOLIDWORKS\eDrawings\) or look for eDrawings in Add/Remove Programs. Query the installed version via the executable properties or registry key if available.
    Affected if eDrawings 2025 is installed and running version 2025 (any build) without the vendor patch applied.
  2. Identify the installed eDrawings version
    Right-click on eDrawings.exe, select Properties, and check the File Version field. Alternatively, run 'eDrawings.exe -version' if supported, or check the version in the Windows registry under HKLM\SOFTWARE\SOLIDWORKS\eDrawings\ or HKLM\SOFTWARE\WOW6432Node\SOLIDWORKS\eDrawings\.
    Affected if The version falls within the 2025 release line and is prior to the patched version released by SOLIDWORKS.
  3. Confirm SLDPRT file association is enabled
    Open Default Apps in Windows Settings, click on eDrawings under 'Choose defaults by app', and verify whether .sldPRT is listed in the supported file types. Alternatively, check the registry key HKCR\.sldPRT\OpenWithProgids or HKCR\sldPRTfile\shell\open\command.
    Affected if The SLDPRT file extension is associated with eDrawings, meaning opening such files will trigger the vulnerable parser.
  4. Check for recent SLDPRT file processing activity
    Review Windows Event Logs (Application and Security) for eDrawings events, or check the application's recent files list if accessible. Examine the user's recent documents folder for any recently opened SLDPRT files.
    Affected if The user has opened untrusted or unexpected SLDPRT files with eDrawings 2025, which could have triggered the vulnerability.
  5. Inspect for indicators of compromise
    Run antivirus/EDR scans on the system and review any alerts related to eDrawings. Check for unexpected DLL injections or memory anomalies associated with the eDrawings process.
    Affected if The system shows signs of exploitation such as unexpected code execution, memory corruption detected by security tools, or unauthorized system changes following SLDPRT file handling.

A user is affected if eDrawings 2025 is installed with an unpatched version and has SLDPRT file associations enabled, particularly if untrusted SLDPRT files have been opened.

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

Apply the vendor patch from SOLIDWORKS when released. Until then, instruct users to avoid opening SLDPRT files from untrusted sources and consider disabling eDrawings file associations or running the application in a sandbox.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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