CVE-2025-48746
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) v.11.0.0.0 and before, as well as after v.11.1.25134.03 lacks Authentication for a Critical Function.
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 versions 11.0.0.0 and before, as well as versions after 11.1.25134.03, contain a critical authentication bypass vulnerability where a specific function lacks proper authentication enforcement, allowing unauthenticated attackers to access sensitive operations.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Netwrix Directory Manager versionCheck the application version through the GUI (Help > About) or by inspecting the installed program's version metadata. Common locations: Program Files\Netwrix\Directory Manager\ or check the application manifest/config file.Affected if Installed version is 11.0.0.0 or lower, OR installed version is 11.1.25134.03 or higher (the safe version range is > 11.0.0.0 and <= 11.1.25134.03)
-
Locate the affected authentication-critical functionReview application endpoint configuration or API documentation to identify the specific function that lacks authentication enforcement. This is typically a sensitive operations endpoint (such as user management, configuration, or administrative functions).Affected if The vulnerable function endpoint exists in the deployment and is network-accessible
-
Verify authentication is enforced on the sensitive functionAttempt an unauthenticated HTTP request (using curl or similar tool) to the suspected function endpoint. Send a request without any session token, cookie, or authentication header.Affected if The request succeeds without returning an authentication error (401 Unauthorized or redirect to login), indicating the function accepts unauthenticated requests
-
Inspect authentication configuration filesExamine application configuration files (web.config, app.config, or similar) for the specific function's authentication settings. Look for authorization rules, authentication modules, or permission settings.Affected if The configuration shows no authentication requirement defined for the affected function, or authentication is explicitly disabled for that endpoint
You are affected if your installed Netwrix Directory Manager version falls outside the safe range (> 11.0.0.0 and <= 11.1.25134.03) AND the vulnerable function is accessible without credentials.
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.
From vendor dataImplement robust authentication checks for the affected critical function, ensuring all requests to this endpoint require valid credentials and session validation.
- Consultation6.0 h
- Implementation10.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 $7,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48746 — 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-48746 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