CVE-2025-47760
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 · uneditedV-SFT v6.2.5.0 and earlier contains an issue with stack-based buffer overflow in VS6MemInIF!set_temp_type_default function. Opening specially crafted V7 or V8 files may lead to crash, information disclosure, and arbitrary code execution.
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 confidenceV-SFT v6.2.5.0 and earlier contains a stack-based buffer overflow in the VS6MemInIF!set_temp_type_default function. When the application opens specially crafted V7 or V8 files, the lack of proper bounds checking allows an attacker to overwrite stack memory, leading to potential crash, information disclosure, and arbitrary code execution.
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>= 6.0.1.0, < 6.2.6.0CVSS 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.
-
Identify installed V-SFT versionCheck the application's About dialog, installation directory version file, or registry entry for Monitouch V Sft versionAffected if installed version is 6.0.1.0 through 6.2.5.0 inclusive (falls in >= 6.0.1.0 and < 6.2.6.0)
-
Confirm V7/V8 file support is presentVerify the V-SFT installation includes libraries or modules capable of parsing V7 or V8 file formats (look for V7/V8 related DLLs, file open dialog filters, or documentation)Affected if V7 or V8 file parsing capability exists in the installation
-
Verify vulnerable function existsExamine the VS6MemInIF module/DLL for the presence of set_temp_type_default function using tools like dumpbin, strings, or a disassemblerAffected if the set_temp_type_default function is found in the VS6MemInIF module
-
Check for recent V7/V8 file operationsReview application logs, recent documents, or audit logs for openings of .v7 or .v8 project filesAffected if the application has recently opened or currently has V7 or V8 format files loaded
User is affected if V-SFT version is 6.0.1.0 through 6.2.5.0 and the application handles V7 or V8 files with the vulnerable set_temp_type_default function present.
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 · scoped6.2.6.0
Upgrade V-SFT to a version beyond 6.2.5.0 if a patch is available; otherwise, avoid opening untrusted V7 or V8 files until a fix can be applied.
V-SFT version 6.2.6.0 or later
- Identify the current installed version of Monitouch V SFT (V-SFT) on the system
- Obtain V-SFT version 6.2.6.0 or later from the official Fujielectric Monitouch vendor source (monitouch.fujielectric.com)
- Follow the vendor's standard upgrade procedure to install version 6.2.6.0 or newer
- After upgrade, verify the installed version is 6.2.6.0 or higher
- Exercise caution when opening V7 or V8 files from untrusted sources until the upgrade is complete
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.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 $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47760 — 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-47760 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