CVE-2025-61860
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 · uneditedAn out-of-bounds read vulnerability exists in VS6MemInIF!set_temp_type_default of V-SFT v6.2.7.0 and earlier. Opening specially crafted V-SFT files may lead to information disclosure, affected system's abnormal end (ABEND), 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 confidenceAn out-of-bounds read vulnerability in the set_temp_type_default function of V-SFT v6.2.7.0 and earlier allows specially crafted V-SFT files to read memory beyond allocated boundaries, potentially exposing sensitive data, causing system crash (ABEND), or enabling 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.2.7.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 installed V-SFT versionLocate and open the Monitouch V SFT application, then navigate to Help > About or check the installation directory for version information (typically in an 'About' dialog or version.txt file)Affected if The displayed version is 6.2.7.0 or earlier, meaning the software contains the vulnerable set_temp_type_default function
-
Confirm V-SFT file processing is enabledCheck if the V-SFT application is configured to open or parse .vsf or related V-SFT file types; look for file association settings or import/export configurations within the softwareAffected if V-SFT file parsing is active, as the vulnerability triggers when specially crafted V-SFT files are opened in the application
-
Review application logs for crashes or ABEND eventsExamine V-SFT application logs, Windows Event Viewer application logs, or any crash dump files in the software's log directory for entries mentioning 'ABEND', access violations, or out-of-bounds read errorsAffected if Crash or ABEND logs exist that reference the set_temp_type_default function or memory access violations during V-SFT file operations
-
Inspect recent V-SFT files for tamperingCheck the modification timestamps and file hashes of V-SFT project files in your environment, comparing against known-good baselines or backupsAffected if V-SFT files show unexpected modification dates or fail integrity checks against known-good hashes, suggesting possible malicious file introduction
A system is affected if Monitouch V SFT version 6.2.7.0 or earlier is installed AND the software is configured to process V-SFT files, as the out-of-bounds read vulnerability in set_temp_type_default triggers upon opening specially crafted files.
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.
From vendor dataAvoid opening V-SFT files from untrusted sources; obtain and apply vendor patch when available; implement file sanitization or sandboxing as compensating control until patch is deployed.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61860 — 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-61860 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