dbcve.org
Directory ManagerApplication · Netwrix

CVE-2025-47748

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-28
Fix available
A fix is available. Upgrade to 11.1.25134.03 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 v.11.0.0.0 and before & after v.11.1.25134.03 contains a hardcoded password.

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

Netwrix Directory Manager contains a hardcoded password embedded in the application code or configuration files. This exposes authentication credentials that could be discovered through code review, reverse engineering, or configuration analysis, potentially allowing unauthorized access to the application or associated systems.

MitigationUpdate to the latest version (after v.11.1.25134.03) to remove the hardcoded password, rotate any exposed credentials, and implement secure credential storage (e.g., secrets manager, environment variables, or encrypted configuration).

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.25134.03

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Check Netwrix Directory Manager version
    Open the application, go to Help > About, or check the installed software list in Programs and Features. Alternatively, check the installation directory for a version file or check the Windows registry under HKLM\SOFTWARE\Netwrix for the version value.
    Affected if The installed version is 11.0.0.0 through 11.1.25134.02 (inclusive), meaning it is less than 11.1.25134.03.
  2. Search configuration files for hardcoded passwords
    Inspect all XML, JSON, INI, and config files in the Netwrix Directory Manager installation directory (typically C:\Program Files\Netwrix Directory Manager\). Look for password, pwd, pass, or credential fields with plaintext values. Use a text search utility to scan for strings like 'password=', 'pwd=', or base64-encoded credential patterns.
    Affected if Any configuration file contains a hardcoded password string that is not masked or encrypted.
  3. Search application binaries and scripts for password strings
    Use a tool like strings (Sysinternals), grep, or a hex editor to scan executable files (.exe, .dll) in the installation folder for plaintext password patterns. Also check any .ps1, .bat, or .sql scripts in the application directory for embedded credentials.
    Affected if Binaries or scripts contain readable password strings, especially if they appear in multiple locations or follow a pattern of being embedded directly in code.
  4. Review connection strings in database configuration
    Check any database connection configuration files (often named connection.config, db.config, or similar) for SQL or LDAP connection strings. Inspect whether they contain embedded credentials rather than referencing environment variables or a secrets vault.
    Affected if Connection strings contain username and password fields with plaintext values instead of integrated authentication or secure credential storage.

You are affected if your Netwrix Directory Manager version is between 11.0.0.0 and 11.1.25134.02 AND any configuration files, application binaries, or scripts in the installation directory contain hardcoded plaintext passwords.

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.25134.03 or later
Fixed in 11.1.25134.03
Interim mitigation

Update to the latest version (after v.11.1.25134.03) to remove the hardcoded password, rotate any exposed credentials, and implement secure credential storage (e.g., secrets manager, environment variables, or encrypted configuration).

Recommended fix High confidence

11.1.25134.03

  1. Download Netwrix Directory Manager version 11.1.25134.03 or later from the official Netwrix portal
  2. Review the release notes for version 11.1.25134.03 to understand any configuration or migration requirements
  3. Create a complete backup of the current Directory Manager installation and database
  4. Stop all Directory Manager services before upgrading
  5. Install version 11.1.25134.03 using the standard upgrade procedure
  6. Verify that the hardcoded password vulnerability has been remediated by reviewing configuration files for removal of embedded credentials
  7. Restart Directory Manager services and verify normal operation
  8. Confirm the upgraded version by checking the applicationAbout or version information

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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