CVE-2025-47728
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 · uneditedDelta Electronics CNCSoft-G2 lacks proper validation of the user-supplied file. If a user opens a malicious file, an attacker can leverage this vulnerability to execute 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 confidenceDelta Electronics CNCSoft-G2 lacks proper validation of user-supplied files. An attacker can craft a malicious file that, when opened by a user, allows arbitrary code execution in the context of the current process due to insufficient input validation during file parsing.
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< 2.1.0.27CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check if CNCSoft-G2 is installedLook for CNCSoft-G2 in the list of installed programs on the system (Control Panel > Programs and Features, or via registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall)Affected if CNCSoft-G2 is present on the system
-
Identify the installed versionCheck the program's version information - right-click the executable, view Properties > Details, or check the uninstall registry entry for the DisplayVersion valueAffected if The version displayed is below 2.1.0.27 (for example, 2.1.0.26, 2.0.x, 1.x, etc.)
-
Confirm the file parsing component is in useDetermine if the software is used to open, import, or process CNC project files, G-code files, or other machine configuration filesAffected if Users routinely open files from untrusted sources in CNCSoft-G2
-
Check for recent file processing activityReview recent documents or recent files opened within CNCSoft-G2, or examine the application's file handling logs if availableAffected if Unknown or untrusted files have been opened recently in the software
You are affected if CNCSoft-G2 is installed and the version is below 2.1.0.27, and the software is used to open user-supplied files.
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.
dbcve · scoped2.1.0.27
Users should avoid opening untrusted or unverified files in CNCSoft-G2. The vendor should implement comprehensive file validation and sanitization checks before processing any user-supplied files.
CNCSoft-G2 version 2.1.0.27
- Identify the current version of CNCSoft-G2 installed on the system
- Download version 2.1.0.27 or later from the vendor's official file center (filecenter.deltaww.com)
- Close any running instances of CNCSoft-G2
- Run the installer for the new version, following the on-screen prompts
- After installation, verify the version number matches 2.1.0.27 or higher
- Test that the application launches and functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47728 — 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-47728 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