dbcve.org
Directory ManagerApplication · Netwrix

CVE-2025-54396

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-07
Fix available
A fix is available. Upgrade to 11.1.25162.02 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Netwrix Directory Manager (formerly Imanami GroupID) 11.0.0.0 before 11.1.25162.02 allows SQL Injection. Authenticated users can exploit this.

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

SQL Injection vulnerability in Netwrix Directory Manager allows authenticated users to inject malicious SQL queries through unsanitized input fields or parameters, potentially enabling unauthorized data access, modification, or deletion in the underlying database.

MitigationUpdate to version 11.1.25162.02 or later which contains the patch. If immediate patching is not feasible, restrict application access to trusted authenticated users only and implement intensive database query logging and monitoring for suspicious activity.

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
Directory ManagerApplication
Affected:>= 11.0.0.0, < 11.1.25162.02

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Netwrix Directory Manager installation
    Check the Windows Program Files directory for 'Netwrix Directory Manager' folder, or look for the service in Windows Services named 'Netwrix Directory Manager Service'
    Affected if The software is present on the system
  2. Determine installed version
    Open Windows Services, locate the Netwrix Directory Manager service, right-click and view Properties, or check the version from the application's About/Help section
    Affected if The version is 11.0.0.0 through 11.1.25162.01 inclusive (versions less than 11.1.25162.02)
  3. Verify application authentication configuration
    Review the Netwrix Directory Manager web application or console settings to confirm whether authentication is properly enforced and identify which user accounts have access
    Affected if Untrusted or unauthorized user accounts can authenticate to the application
  4. Assess network exposure
    Check firewall rules or IIS/Apache bindings to determine if the Netwrix Directory Manager web interface is accessible from untrusted networks
    Affected if The application is exposed to the internet or untrusted internal networks without proper access restrictions
  5. Review database query logging
    Inspect the Netwrix Directory Manager configuration or database server settings to determine if detailed SQL query logging is enabled
    Affected if SQL query logging and monitoring are not active, preventing detection of suspicious database activity

A user is affected if Netwrix Directory Manager version 11.0.0.0 through 11.1.25162.01 is installed and the application allows untrusted authenticated users to submit input that reaches the database.

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

Update to version 11.1.25162.02 or later which contains the patch. If immediate patching is not feasible, restrict application access to trusted authenticated users only and implement intensive database query logging and monitoring for suspicious activity.

Recommended fix Moderate confidence

11.1.25162.02 or later

  1. 1. Back up the current Netwrix Directory Manager database and configuration.
  2. 2. Download the fixed version (11.1.25162.02 or later) from the official Netwrix download portal or vendor support site.
  3. 3. Stop the Directory Manager service before applying the update.
  4. 4. Install the updated version following the vendor's standard upgrade procedure.
  5. 5. Verify the upgrade was successful by checking the application version.
  6. 6. Test that Directory Manager functionality works correctly after the upgrade.
  7. 7. Validate that the SQL injection vulnerability is no longer present.

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

Fix this in Directory Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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