dbcve.org
Imagedirector CaptureApplication · Milner

CVE-2025-58740

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 7.6.3.25808 or later.
See remediation →
57/100
Remediation priority · Elevated
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
The use of a hard-coded encryption key in calls to the Password function in C2SGlobalSettings.dll in Milner ImageDirector Capture on Windows allows a local attacker to decrypt database credentials by reading the cryptographic key from the executable. This issue affects ImageDirector Capture: from 7.0.9 before 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 · high confidence

Milner ImageDirector Capture contains a hard-coded encryption key embedded in C2SGlobalSettings.dll's Password function. A local attacker with read access to the executable can extract this key and decrypt stored database credentials, leading to unauthorized database access.

MitigationUpdate to ImageDirector Capture version 7.6.3.25808 or later to obtain a version with proper key management. If immediate patching is not feasible, restrict filesystem access to the executable and consider rotating exposed database credentials.

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

CVSS:3.1/AV:L/AC:L/PR:L/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
    Check the program's version through Windows Add/Remove Programs, or right-click the main executable and select Properties > Details to view File Version. Compare this version number against the vulnerable range: >= 7.0.9 and < 7.6.3.25808.
    Affected if The installed version falls within 7.0.9 up to but not including 7.6.3.25808.
  2. Locate C2SGlobalSettings.dll
    Search for C2SGlobalSettings.dll within the ImageDirector Capture installation directory, typically found in the application root folder or a subfolder like /bin or /lib.
    Affected if The DLL file exists in the installation directory, indicating the component with the hard-coded key is present.
  3. Verify hard-coded key presence in Password function
    Open C2SGlobalSettings.dll in a disassembler, decompiler, or hex editor and locate the Password function. Look for a static or hard-coded string value used as an encryption key, rather than a dynamically generated or externally sourced key.
    Affected if A hard-coded encryption key string is found embedded within the Password function code.
  4. Check for stored encrypted database credentials
    Inspect configuration files, registry entries, or database connection files within the ImageDirector Capture installation for encrypted credential strings. These may be in files like config.xml, settings.ini, or a local database file.
    Affected if Encrypted database credentials exist in stored configuration or database files that could be decrypted using the extracted key.

You are affected if ImageDirector Capture version is between 7.0.9 and 7.6.3.25808 (inclusive of lower bound, exclusive of upper) and the C2SGlobalSettings.dll contains the hard-coded encryption key.

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

Update to ImageDirector Capture version 7.6.3.25808 or later to obtain a version with proper key management. If immediate patching is not feasible, restrict filesystem access to the executable and consider rotating exposed database credentials.

Recommended fix High confidence

7.6.3.25808 or later

  1. 1. Identify the current installed version of ImageDirector Capture on the system
  2. 2. If the version is >= 7.0.9 and < 7.6.3.25808, the system is vulnerable
  3. 3. Prior to upgrading, create a full backup of the ImageDirector Capture installation and configuration
  4. 4. Obtain and install ImageDirector Capture version 7.6.3.25808 or later from the vendor
  5. 5. After upgrade, verify the C2SGlobalSettings.dll has been updated and no longer contains the hard-coded encryption key
  6. 6. Confirm database credentials are now using properly managed encryption rather than hard-coded keys

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

Fix this in Imagedirector Capture Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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