CVE-2025-58744
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 · uneditedUse of Default Credentials, Hard-coded Credentials vulnerability in C2SGlobalSettings.dll in Milner ImageDirector Capture on Windows allows decryption of document archive files using credentials decrypted with hard-coded application encryption key. This issue affects ImageDirector Capture: from 7.0.9.0 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 confidenceThe vulnerability exists in C2SGlobalSettings.dll where application credentials used to decrypt document archive files are protected using a hard-coded encryption key embedded in the software. An attacker with access to the application or its binaries can extract this hard-coded key and decrypt sensitive document archives without proper authorization.
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>= 7.0.9, < 7.6.3.25808CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Milner Imagedirector Capture is installedCheck the system for Milner Imagedirector Capture by reviewing installed programs in Windows Control Panel > Programs and Features, or use a software inventory tool to scan for this application.Affected if The application is present on the system.
-
Identify the installed version of Milner Imagedirector CaptureLocate the application in the installed programs list and note the version number shown, or right-click on the main executable or C2SGlobalSettings.dll and select Properties > Details to view the File Version.Affected if The version falls within the range >= 7.0.9 and < 7.6.3.25808.
-
Locate C2SGlobalSettings.dllSearch the installation directory of Milner Imagedirector Capture for the file C2SGlobalSettings.dll. Common locations include C:\Program Files\Milner\ or the application's installation folder.Affected if The DLL file exists in the application directory.
-
Verify the DLL version matches affected releaseRight-click on C2SGlobalSettings.dll, select Properties > Details, and compare the File Version to the affected range (7.0.9 through 7.6.3.25808).Affected if The DLL version is 7.0.9 or higher but below 7.6.3.25808.
A user is affected if Milner Imagedirector Capture is installed with a version between 7.0.9 and 7.6.3.25808 (exclusive), as this version range contains the vulnerable C2SGlobalSettings.dll with the hard-coded encryption key.
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.
dbcve · scoped7.6.3.25808
Update Milner ImageDirector Capture to version 7.6.3.25808 or later which removes the hard-coded encryption key. If immediate patching is not possible, restrict access to the application binaries and monitor for unauthorized access attempts.
ImageDirector Capture 7.6.3.25808 or later
- Verify current ImageDirector Capture version via Help > About or Windows Programs and Features
- Backup all configuration files, custom templates, and document archives
- Download ImageDirector Capture version 7.6.3.25808 or later from the official vendor portal or trusted distribution channel
- Stop any running ImageDirector Capture services or applications
- Run the installer with administrator privileges
- Follow the installation wizard prompts, preserving existing settings if prompted
- Restart the ImageDirector Capture service
- Verify the application launches correctly and document archives are accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58744 — 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-58744 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