CVE-2025-6972
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 · uneditedUse After Free vulnerability exists in the CATPRODUCT 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 CATPRODUCT 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 confidenceA Use After Free vulnerability exists in the CATPRODUCT file parsing routine of SOLIDWORKS eDrawings 2025. When opening a specially crafted CATPRODUCT file, the software frees memory but subsequently attempts to access the freed pointer, leading to arbitrary code execution. The attack requires user interaction to open the malicious file.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify eDrawings 2025 is installedCheck the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look in C:\Program Files\SOLIDWORKS eDrawings for the eDrawings.exe executableAffected if eDrawings 2025 is found on the system
-
Confirm the exact eDrawings versionRight-click eDrawings.exe, select Properties, and check the File Version field under the Details tab. Alternatively, run eDrawings and go to Help > About eDrawingsAffected if The version is any release of eDrawings 2025 (check if version starts with 2025)
-
Check for CATPRODUCT file type associationsOpen Default Programs or view HKEY_CLASSES_ROOT\.CATPRODUCT in the registry to see if eDrawings is registered to handle CATPRODUCT filesAffected if eDrawings is registered as the handler for .CATPRODUCT files
-
Inspect recent file access eventsOpen Windows Event Viewer > Security and filter by Event ID 4656 or use PowerShell to search for recent accesses to .CATPRODUCT files in the user's Recent folderAffected if There are recent .CATPRODUCT files opened by eDrawings on this system
-
Review application crash logsCheck the eDrawings crash dump folder (typically %APPDATA%\SOLIDWORKS eDrawings\CrashDumps or Windows Problem Reports) for any recent crashes related to CATPRODUCT parsingAffected if Recent crashes occurred when opening CATPRODUCT files
The system is affected if eDrawings 2025 is installed, handles .CATPRODUCT files, and those files have been opened recently.
Generated from the published advisory. Verify against your own configuration.
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 dataDo not open CATPRODUCT files from untrusted sources. Wait for and apply the vendor-supplied patch from SOLIDWORKS. Consider network isolation or additional sandboxing for eDrawings until the patch is available.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6972 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6972 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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