dbcve.org
Monitouch V SftApplication · Fujielectric

CVE-2025-47749

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 free of pointer not at start of buffer in VS6EditData.dll!CWinFontInf::WinFontMsgCheck 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 a memory corruption vulnerability in VS6EditData.dll's CWinFontInf::WinFontMsgCheck function where the code attempts to free a pointer that is not at the start of an allocated buffer. Opening specially crafted V7 or V8 files triggers this improper memory deallocation, potentially allowing an attacker to corrupt heap metadata, cause crashes, leak sensitive memory contents, or achieve arbitrary code execution.

MitigationAvoid opening untrusted or specially crafted V7 or V8 files in vulnerable V-SFT versions. Apply vendor patches when released. Consider running V-SFT in a sandboxed or isolated environment as a defense-in-depth measure.

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 V-SFT installation and version
    Check the installed version of Monitouch V Sft in the application directory or Windows Programs list. Common paths include C:\Program Files\Fujielectric\Monitouch V Sft\ or check Add/Remove Programs.
    Affected if The installed version is 6.0.1.0 through 6.2.5.0 inclusive (anything >= 6.0.1.0 and < 6.2.6.0)
  2. Verify VS6EditData.dll presence
    Locate the file VS6EditData.dll in the V-SFT installation directory. This DLL contains the vulnerable CWinFontInf::WinFontMsgCheck function.
    Affected if VS6EditData.dll exists in the V-SFT installation folder and its version matches the affected V-SFT versions
  3. Check for V7 and V8 file handling capability
    Determine if the V-SFT installation includes support for opening V7 or V8 project files. This is typically the default functionality in affected versions.
    Affected if The system can open or has recently opened V7 or V8 format project files using V-SFT
  4. Confirm version is below fixed release
    Compare your installed V-SFT version number to the vendor's fixed version 6.2.6.0. Any version below 6.2.6.0 within the 6.0.x.x to 6.2.5.x range is affected.
    Affected if The installed version is lower than 6.2.6.0 and was released after 6.0.1.0

You are affected if V-SFT version 6.0.1.0 through 6.2.5.0 is installed and the software is used to open V7 or V8 project files.

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

Avoid opening untrusted or specially crafted V7 or V8 files in vulnerable V-SFT versions. Apply vendor patches when released. Consider running V-SFT in a sandboxed or isolated environment as a defense-in-depth measure.

Recommended fix High confidence

V-SFT version 6.2.6.0 or later

  1. 1. Backup all existing V-SFT projects and configuration files before proceeding with the upgrade.
  2. 2. Navigate to the official Monitouch vendor website (monitouch.fujielectric.com) or contact authorized distributors to obtain V-SFT version 6.2.6.0 or later.
  3. 3. Uninstall the current vulnerable version of V-SFT from the system.
  4. 4. Install the downloaded fixed version (6.2.6.0 or later).
  5. 5. After installation, verify the version number matches the fixed release.
  6. 6. Re-open existing V7 or V8 project files to confirm normal functionality.
  7. 7. Ensure that any specially crafted or untrusted V7/V8 files are not opened until the upgrade is confirmed working.
Caveat Review vendor release notes for any changes in file format compatibility or feature modifications between your current version and 6.2.6.0

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

Fix this in Monitouch V Sft Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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