dbcve.org
Imagedirector CaptureApplication · Milner

CVE-2025-58741

HIGH · 7.5 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 7.6.3.25808 or later.
See remediation →
84/100
Remediation priority · High
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
Insufficiently Protected Credentials vulnerability in the Credential Field of Milner ImageDirector Capture allows retrieval of credential material and enables database access.This issue affects ImageDirector Capture: from 7.0.9 through 7.6.3.25808.

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

The ImageDirector Capture application stores credentials in a field without sufficient protection, allowing attackers to retrieve the credential material. This exposure enables unauthorized database access.

MitigationApply the vendor patch to upgrade ImageDirector Capture beyond version 7.6.3.25808 and rotate any credentials that may have been exposed.

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
Imagedirector CaptureApplication
Affected:>= 7.0.9, < 7.6.3.25808

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 ImageDirector Capture version
    Locate the ImageDirector Capture installation and retrieve its version number, typically found in the application itself, an about dialog, or installation metadata
    Affected if The installed version is >= 7.0.9 and < 7.6.3.25808
  2. Locate credential storage locations
    Identify where ImageDirector Capture stores credentials for database access - check application configuration files, database connection settings, or embedded credential fields within the application
    Affected if Credentials are stored in any location within the application
  3. Inspect credential protection mechanism
    Examine the stored credentials to determine the protection method applied - check if they appear in plaintext, encoded, encrypted, or hashed
    Affected if Credentials are stored without adequate encryption or are stored in an unprotected field format
  4. Verify database authentication configuration
    Check if ImageDirector Capture is configured to authenticate to a database using stored credentials and confirm those credentials are accessible through the vulnerable storage mechanism
    Affected if The application uses its internal credential storage to authenticate to external databases

The environment is affected if ImageDirector Capture version 7.0.9 through 7.6.3.25808 is installed and credentials for database authentication are stored in unprotected application fields accessible to users.

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 7.6.3.25808 or later
Fixed in 7.6.3.25808
Interim mitigation

Apply the vendor patch to upgrade ImageDirector Capture beyond version 7.6.3.25808 and rotate any credentials that may have been exposed.

Recommended fix High confidence

ImageDirector Capture 7.6.3.25808 or later

  1. 1. Identify current ImageDirector Capture version by checking the application's 'About' section or system information
  2. 2. Download ImageDirector Capture version 7.6.3.25808 or later from the official Milner vendor support portal
  3. 3. Create a full backup of the current database and configuration files before upgrading
  4. 4. Stop the ImageDirector Capture service
  5. 5. Install the upgraded version (7.6.3.25808 or newer) following vendor installation documentation
  6. 6. Restart the ImageDirector Capture service
  7. 7. Verify the credential field now properly encrypts or protects stored credentials
  8. 8. Confirm database access controls are functioning as expected post-upgrade
Caveat Review release notes for any configuration or database schema changes between your current version and 7.6.3.25808; test in non-production environment first

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

Fix this in Imagedirector Capture Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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