CVE-2025-54393
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 allows Static Code Injection. Authenticated users can obtain administrative access.
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 a static code injection vulnerability that allows authenticated users to inject malicious code that executes with elevated privileges, enabling privilege escalation to administrative access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Identify installed versionLocate the version information for Netwrix Directory Manager (formerly Imanami GroupID) in the product's about dialog, installation directory, or control panel programs list. Common locations include the Help menu, a version.txt file, or the installer metadata.Affected if The installed version is 11.0.0.0 through 11.1.25162.01 inclusive (any version >= 11.0.0.0 but < 11.1.25162.02)
-
Confirm authentication is requiredVerify that user authentication is enabled and configured for Netwrix Directory Manager. This may be confirmed through the administrative console, user management settings, or authentication configuration files.Affected if Authenticated user access is permitted and the application accepts user sessions
-
Locate code injection entry pointIdentify any feature within Netwrix Directory Manager that accepts static code input from users, such as custom scripts, template modifications, or configuration-based code entry points. Examine administrative interfaces where users can supply code or script content.Affected if A feature allowing user-supplied code or script execution is accessible to authenticated non-administrative users
You are affected if your installed Netwrix Directory Manager version falls between 11.0.0.0 and 11.1.25162.01, authentication is enabled, and a code injection入口点 exists that accepts authenticated user input.
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 to remediate this vulnerability.
11.1.25162.02 or later
- 1. Identify the current installed version of Netwrix Directory Manager by checking the application UI or system information
- 2. Review the current configuration and document existing settings that may need to be reconfigured after upgrade
- 3. Create a complete backup of the current Directory Manager configuration and database
- 4. Plan maintenance window for the upgrade process
- 5. Upgrade to version 11.1.25162.02 or a later stable release following vendor documentation
- 6. After upgrade, verify the application is functioning correctly
- 7. Confirm the vulnerability is resolved by testing that unauthenticated or low-privilege authenticated users cannot inject commands
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54393 — 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-54393 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