dbcve.org
Monitouch V SftApplication · Fujielectric

CVE-2025-47755

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 VS6EditData!VS4_SaveEnvFile 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 the VS6EditData!VS4_SaveEnvFile function. Opening specially crafted V7 or V8 files triggers the vulnerability, potentially causing a crash, leaking sensitive information from memory, or enabling arbitrary code execution.

MitigationUpdate to a version newer than v6.2.5.0 when available, or avoid opening untrusted V7 or V8 files until a patch is applied.

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 installed V-SFT version
    Locate the V-SFT installation directory and find the version information (typically in an About dialog, installer, or version file within the program folder). Compare the installed version to the affected range: versions 6.0.1.0 through 6.2.5.0 are vulnerable.
    Affected if The installed version is 6.0.1.0 or higher but lower than 6.2.6.0
  2. Verify VS6EditData component is present
    Search for the file VS6EditData.dll or VS6EditData.exe within the V-SFT installation directory, as this contains the vulnerable VS4_SaveEnvFile function.
    Affected if The VS6EditData component exists in the installation folder
  3. Confirm V7/V8 file handling capability
    Check whether the V-SFT installation includes support for opening or importing V7 or V8 format files (this may be indicated in file open dialogs, supported formats documentation, or registry entries).
    Affected if V7 or V8 file support is enabled or available in the installation
  4. Inspect for crash events related to file parsing
    Review application event logs, crash dumps, or error logs for incidents occurring when opening V7 or V8 files, particularly errors mentioning VS4_SaveEnvFile or memory access violations.
    Affected if Crashes or access violations occur specifically when opening V7 or V8 files

A user is affected if V-SFT version 6.0.1.0 through 6.2.5.0 is installed and the VS6EditData component with V7/V8 file support is present and used to open untrusted 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

Update to a version newer than v6.2.5.0 when available, or avoid opening untrusted V7 or V8 files until a patch is applied.

Recommended fix High confidence

V-SFT version 6.2.6.0 or later

  1. 1. Identify the currently installed version of Monitouch V-SFT on the system
  2. 2. Download V-SFT version 6.2.6.0 or later from the official vendor (Monitouch/Fuji Electric)
  3. 3. Follow the vendor's standard upgrade procedure to apply the update
  4. 4. Verify the installation by checking that the new version is >= 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

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