dbcve.org
Monitouch V SftApplication · Fujielectric

CVE-2025-47752

HIGH · 7.8 CVSS v3.1 Published 2025-05-19
Fix available
A fix is available. Upgrade to 6.2.6.0 or later.
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
V-SFT v6.2.5.0 and earlier contains an issue with out-of-bounds write in VS6ComFile!MakeItemGlidZahyou 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 confidence

V-SFT v6.2.5.0 and earlier contains an out-of-bounds write vulnerability in the VS6ComFile!MakeItemGlidZahyou function when parsing specially crafted V7 or V8 files. This memory corruption vulnerability can be triggered when a user opens a malicious file, potentially leading to application crash, information disclosure, or arbitrary code execution.

MitigationUsers should avoid opening untrusted V7 or V8 files until the vendor releases a patch that adds proper bounds checking in the MakeItemGlidZahyou function. Implementing input validation and sandboxing around file parsing operations can provide additional defense-in-depth protection.

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
Monitouch V SftApplication
Affected:>= 6.0.1.0, < 6.2.6.0

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. Identify if Monitouch V Sft is installed
    Check the system for V-SFT installation by looking in Program Files for Fujielectric Monitouch V-Sft folder, or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Monitouch V Sft or similar Fujielectric product
    Affected if V-SFT is not found on the system, this CVE does not apply
  2. Determine the installed V-SFT version
    Locate the main V-SFT executable (typically named V-SFT.exe or similar) and view its file properties to find the Product Version, or check the registry Uninstall entry for the Version value
    Affected if The version cannot be determined or the product is not installed
  3. Compare version against affected range
    Parse the version number found (format is X.X.X.X) and check if it falls within >= 6.0.1.0 and < 6.2.6.0. Any version from 6.0.1.0 through 6.2.5.0 is affected
    Affected if Installed version is 6.0.1.0, 6.2.0.0, 6.2.5.0 or any version between 6.0.1.0 and 6.2.5.0 inclusive
  4. Verify VS6ComFile component presence
    Search for VS6ComFile.dll or VS6ComFile.sys in the V-SFT installation directory, as this module contains the vulnerable MakeItemGlidZahyou function
    Affected if The VS6ComFile component exists in the installation folder, indicating the vulnerable code is present
  5. Confirm file association with V7/V8 files
    Check if the system has file associations for .v7 or .v8 file extensions linked to V-SFT, or check if users commonly import these file types into the application
    Affected if V-SFT processes or imports V7/V8 files, as this is the attack vector required to trigger the vulnerability

The environment is affected if Monitouch V Sft is installed with version 6.0.1.0 through 6.2.5.0 and the system handles V7 or V8 files, allowing the out-of-bounds write in VS6ComFile!MakeItemGlidZahyou to be triggered.

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.

dbcve · scoped
Upgrade available Upgrade to 6.2.6.0 or later
Fixed in 6.2.6.0
Interim mitigation

Users should avoid opening untrusted V7 or V8 files until the vendor releases a patch that adds proper bounds checking in the MakeItemGlidZahyou function. Implementing input validation and sandboxing around file parsing operations can provide additional defense-in-depth protection.

Recommended fix High confidence

6.2.6.0 or later

  1. Identify the current version of Monitouch V Sft (V-SFT) installed on the system.
  2. Navigate to the official vendor website (monitouch.fujielectric.com) or a trusted distribution channel to obtain version 6.2.6.0 or later.
  3. Backup all existing V7/V8 project files and configuration data.
  4. Install the new version (6.2.6.0 or later) following the vendor's installation instructions.
  5. After installation, verify that the installed version is 6.2.6.0 or higher.
  6. Open existing projects to confirm they load correctly and the vulnerability is mitigated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Monitouch V Sft Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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 locally
dbcve dependency scanner

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