dbcve.org
Vision Tools WorkspaceApplication · Millensys

CVE-2025-63958

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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
MILLENSYS Vision Tools Workspace 6.5.0.2585 exposes a sensitive configuration endpoint (/MILLENSYS/settings) that is accessible without authentication. This page leaks plaintext database credentials, file share paths, internal license server configuration, and software update parameters. An unauthenticated attacker can retrieve this information by accessing the endpoint directly, potentially leading to full system compromise. The vulnerability is due to missing access controls on a privileged administrative function.

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

MILLENSYS Vision Tools Workspace 6.5.0.2585 contains an unauthenticated sensitive configuration endpoint at /MILLENSYS/settings that exposes plaintext database credentials, file share paths, internal license server configuration, and software update parameters. The lack of access controls on this administrative function allows any unauthenticated attacker direct access to credentials and internal system details, potentially enabling full system compromise.

MitigationImplement proper authentication and authorization controls on the /MILLENSYS/settings endpoint to ensure only authorized administrators can access sensitive configuration data. Alternatively, restrict network-level access to this endpoint.

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
Vision Tools WorkspaceApplication
Affected:= 5.10.5.2429= 6.5.0.2585= 6.5.0.2596

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed Vision Tools Workspace version
    Check the installed version through the application or its installer. On Windows, look in Add/Remove Programs or check the installation directory for version information files.
    Affected if The installed version matches 5.10.5.2429, 6.5.0.2585, or 6.5.0.2596
  2. Confirm web service is running
    Check if the MILLENSYS web service or application server is running. Look for processes related to MILLENSYS or check if ports (commonly HTTP/HTTPS) used by the application are listening.
    Affected if The web service is active and accessible on the network
  3. Access the vulnerable endpoint without credentials
    Using a web browser or curl command, navigate to http://[hostname]/MILLENSYS/settings or https://[hostname]/MILLENSYS/settings without providing any authentication.
    Affected if The endpoint returns an HTTP 200 response and displays configuration data without requiring login credentials
  4. Verify sensitive data exposure
    Examine the response from the /MILLENSYS/settings endpoint. Look for plaintext database credentials, file share paths, license server details, or update parameters.
    Affected if The response contains plaintext credentials, internal paths, or other sensitive configuration details visible to any unauthenticated user

A user is affected if the MILLENSYS Vision Tools Workspace version is 5.10.5.2429, 6.5.0.2585, or 6.5.0.2596 AND the /MILLENSYS/settings endpoint is accessible without authentication and exposes sensitive configuration data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization controls on the /MILLENSYS/settings endpoint to ensure only authorized administrators can access sensitive configuration data. Alternatively, restrict network-level access to this endpoint.

Fix this in Vision Tools Workspace Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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