CVE-2025-48747
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) before and including v.11.0.0.0 and after v.11.1.25134.03 has Incorrect Permission Assignment for a Critical Resource.
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 has an Incorrect Permission Assignment vulnerability (CWE-732) affecting versions up to 11.0.0.0 and versions after 11.1.25134.03. This allows improper access to a critical resource due to misconfigured permissions, potentially enabling unauthorized users to view, modify, or delete sensitive directory objects.
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.25134.03CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Identify Netwrix Directory Manager versionOpen the application GUI and navigate to Help > About, or check the installation directory for a version file. The version is typically displayed in the main console or can be found in the program's metadata.Affected if The installed version is 11.0.0.0 through 11.1.25134.02 (inclusive). Versions below 11.0.0.0 or at or above 11.1.25134.03 are not affected.
-
Locate the Netwrix Directory Manager installation directoryCommon paths include C:\Program Files\Netwrix\Directory Manager or C:\Program Files (x86)\Netwrix\Directory Manager. Check the primary installation drive for the Netwrix folder.Affected if The installation directory exists and contains the application files.
-
Examine file system permissions on the installation folderRight-click the Netwrix installation folder, select Properties > Security tab. Review the permissions for users and groups. Check if non-administrator accounts or the Everyone group have Full Control, Modify, or Write permissions on critical subfolders (especially those containing configuration files or scripts).Affected if Users other than Administrators or the designated service account have excessive permissions (Full Control, Modify, or Write) on the installation directory or its configuration subfolders.
-
Examine file system permissions on configuration and data directoriesCheck permissions on folders storing configuration files, scripts, and directory object data. Look for overly permissive Access Control Entries (ACEs) that grant excessive access to standard users or domain users.Affected if Standard users or non-privileged groups have permissions that allow viewing, modifying, or deleting sensitive configuration or data files.
-
Review Active Directory permissions if Directory Manager manages AD objectsUsing Active Directory Users and Computers or ADSI Edit, check the permissions on OUs or objects managed by Netwrix Directory Manager. Verify that only authorized service accounts have elevated permissions.Affected if Unauthorized users or groups have permissions to view, modify, or delete directory objects managed by Netwrix Directory Manager.
A system is affected if the installed Netwrix Directory Manager version falls within 11.0.0.0 to 11.1.25134.02 AND overly permissive file system or Active Directory permissions exist on critical resources managed by the application.
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.25134.03
Review and correct file system and Active Directory permissions on critical resources within Netwrix Directory Manager, ensuring least-privilege access controls. Upgrade to a patched version if available from Netwrix support.
11.1.25134.03
- Identify the current installed version of Netwrix Directory Manager
- Download Netwrix Directory Manager version 11.1.25134.03 or later from the official Netwrix download portal
- Review release notes for version 11.1.25134.03 to understand changes and ensure compatibility
- Create a backup of the current configuration and database
- Stop the Netwrix Directory Manager service
- Install the upgrade following standard Netwrix upgrade procedures
- Verify the installation completed successfully
- Start the Netwrix Directory Manager service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48747 — 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-48747 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