CVE-2025-54394
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 · uneditedNetwrix Directory Manager (formerly Imanami GroupID) 11.0.0.0 before 11.1.25162.02 has Insufficiently Protected Credentials for requests to remote Excel resources.
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 confidenceNetwrix Directory Manager (formerly Imanami GroupID) versions 11.0.0.0 through 11.1.25162.01 contain insufficiently protected credentials when making requests to remote Excel resources. This could allow an attacker to intercept or access credentials used to authenticate against remote Excel file sources.
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>= 11.0.0.0, < 11.1.25162.02CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Netwrix Directory Manager installed versionOpen the application or use the program's About/Help section to find the exact version number. Look for a version like 11.0.x.x through 11.1.25162.01.Affected if The installed version falls within 11.0.0.0 through 11.1.25162.01 (inclusive). Versions before 11.0.0.0 or at 11.1.25162.02 and later are not affected.
-
Identify configured Excel data sourcesExamine the Netwrix Directory Manager configuration for any data sources or connectors that access remote Excel files. Look in the admin console, data source settings, or import configurations for Excel-related entries.Affected if Any remote Excel file source is configured and enabled in the product.
-
Review Excel connector authentication settingsCheck the authentication configuration for any Excel import or data source connectors. Look for stored credentials, username/password fields, or authentication methods used when connecting to remote Excel files.Affected if Credentials are stored in plaintext, weakly encrypted, or transmitted without proper protection when connecting to remote Excel resources.
You are affected if the installed version is between 11.0.0.0 and 11.1.25162.01 AND the product is configured to access remote Excel file sources with credentials that are not securely protected.
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 · scoped11.1.25162.02
Upgrade to Netwrix Directory Manager version 11.1.25162.02 or later which addresses the insufficiently protected credentials issue. Until then, restrict network access to trusted Excel file sources and monitor for unauthorized credential access attempts.
11.1.25162.02 or later
- Back up the current Netwrix Directory Manager installation and database
- Download Netwrix Directory Manager version 11.1.25162.02 or later from the vendor's official download portal
- Stop all Directory Manager services before upgrading
- Install the updated version following the vendor's standard upgrade procedure
- Verify the installation completed successfully
- Restart Directory Manager services
- Confirm the vulnerability is resolved by testing remote Excel resource access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-54394 — 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-54394 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