dbcve.org
Monitouch V SftApplication · Fujielectric

CVE-2025-47757

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 read in VS6MemInIF.dll!set_plc_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 · moderate confidence

V-SFT v6.2.5.0 and earlier contains an out-of-bounds read vulnerability in VS6MemInIF.dll's set_plc_type_default function. Opening specially crafted malicious V7 or V8 files triggers the vulnerability, which can cause application crashes, expose sensitive information from memory, and potentially enable arbitrary code execution.

MitigationAvoid opening V7 or V8 files from untrusted or unknown sources until a vendor patch is available. Contact the vendor (presumably Fuji Electric for V-SFT) to confirm patched version availability and apply updates promptly.

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. Check V-SFT installed version
    Open the V-SFT application and navigate to Help > About, or check the program files directory for version information. Compare the installed version against the affected range: >= 6.0.1.0 and < 6.2.6.0.
    Affected if The installed version falls within >= 6.0.1.0 and < 6.2.6.0.
  2. Locate the vulnerable DLL
    Search for VS6MemInIF.dll in the V-SFT installation directory (commonly under Program Files or Program Files (x86)).
    Affected if The DLL exists in the V-SFT installation folder.
  3. Verify V7/V8 file handling capability
    Check if the V-SFT installation supports opening or includes functionality for V7 or V8 project files. Look for file type associations or recent files with .v7 or .v8 extensions.
    Affected if V-SFT is configured to handle or has recently opened V7 or V8 files.
  4. Inspect recent project files
    Examine the V-SFT recent projects list or project directory for .v7 or .v8 files.
    Affected if The environment contains V7 or V8 project files that have been opened.

You are affected if V-SFT version is >= 6.0.1.0 and < 6.2.6.0, the VS6MemInIF.dll is present, and V7 or V8 files can be opened or have been processed.

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 V7 or V8 files from untrusted or unknown sources until a vendor patch is available. Contact the vendor (presumably Fuji Electric for V-SFT) to confirm patched version availability and apply updates promptly.

Recommended fix Moderate confidence

V-SFT version 6.2.6.0 or later

  1. Identify the current installed version of Monitouch V Sft (V-SFT) on the system
  2. Download V-SFT version 6.2.6.0 or later from the official Fujielectric Monitouch website (monitouch.fujielectric.com) or authorized distribution channel
  3. Verify the integrity of the downloaded installer using checksums if provided by the vendor
  4. Close all running instances of V-SFT and any related applications
  5. Run the installer with appropriate privileges and follow the vendor's standard upgrade procedure
  6. After installation, verify the installed version is 6.2.6.0 or higher
  7. Test that normal V7 and V8 file operations function correctly after the upgrade

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

Fix this in Monitouch V Sft Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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