CVE-2025-47756
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 out-of-bounds read in VS6EditData!CGamenDataRom::set_mr400_strc 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 an out-of-bounds read vulnerability in the VS6EditData!CGamenDataRom::set_mr400_strc function when parsing specially crafted V7 or V8 files. The vulnerability allows an attacker to read memory beyond allocated buffers, potentially leading to 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 V-SFT installationLocate the Fujielectric Monitouch V Sft software on the system. Check installation directories, program files, or registry entries for V-SFT, Monitouch, or Fujielectric software.Affected if The V-SFT software is present on the system
-
Verify the vulnerable component existsSearch for the VS6EditData module in the V-SFT installation directory. This module contains the CGamenDataRom::set_mr400_strc function where the vulnerability exists.Affected if The VS6EditData module with the set_mr400_strc function is present on the system
-
Confirm version is in affected rangeDetermine the installed V-SFT version. Compare against the affected range: versions 6.0.1.0 through 6.2.5.0 are vulnerable. Version 6.2.6.0 and later are patched.Affected if Installed version is 6.0.1.0 or higher but lower than 6.2.6.0
-
Assess V7/V8 file processing exposureDetermine if the V-SFT installation is used to open, import, or process V7 or V8 project files. Check file associations, recent file history, or workflow documentation.Affected if V7 or V8 files are opened or processed using this software
The environment is affected if Fujielectric Monitouch V SFT version 6.0.1.0 through 6.2.5.0 is installed AND the software is used to parse V7 or V8 files, which triggers the vulnerable set_mr400_strc function.
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
Until an official patch is available, restrict access to the V-SFT software and avoid opening V7 or V8 files from untrusted sources. Implement file type validation and consider application sandboxing to limit the impact of potential exploitation.
V-SFT version 6.2.6.0 or later
- Identify all systems running Monitouch V SFT (V-SFT) with versions 6.0.1.0 through 6.2.5.0
- Backup all project files and configurations before upgrading
- Obtain V-SFT version 6.2.6.0 or later from the official Fujielectric Monitouch website (monitouch.fujielectric.com) or official distribution channels
- Install the updated version on all affected systems following standard installation procedures
- Verify the upgrade was successful by confirming the software version is 6.2.6.0 or later
- Test that existing V7 and V8 project files open correctly in the updated version
- Re-save project files with the new version to ensure they are not vulnerable to the malformed file exploit
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47756 — 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-47756 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