# CVE-2025-48749: Information disclosure in n/a

> Netwrix Directory Manager leaks sensitive information in sent data, allowing attackers to read confidential details.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2025
- **Updated:** 28 May 2025
- **Also known as:** GHSA-qq2r-6j4w-49qc

## What is CVE-2025-48749?

CVE-2025-48749 is a critical vulnerability in n/a, published on 28 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Netwrix Directory Manager (formerly Imanami GroupID) v11.0.0.0 and before & after v.11.1.25134.03 inserts Sensitive Information into Sent Data.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-48749?

It affects 1 product.


Products: Netwrix Directory Manager.

## How do I fix CVE-2025-48749?

No fix has been published for CVE-2025-48749 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-48749 being exploited?

There is no known exploitation of CVE-2025-48749 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-48748](https://insights.sbomify.com/CVE-2025-48748/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2025-48746](https://insights.sbomify.com/CVE-2025-48746/): Missing authorization in n/a (medium 6.5)
- [CVE-2025-54392](https://insights.sbomify.com/CVE-2025-54392/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-54395](https://insights.sbomify.com/CVE-2025-54395/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-54393](https://insights.sbomify.com/CVE-2025-54393/): Code injection in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48749 and fix it if it is affected.

What it is: CVE-2025-48749 is a critical vulnerability in n/a, published on 28 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48749 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48749/ (Markdown: https://insights.sbomify.com/CVE-2025-48749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48749
- OSV: https://osv.dev/vulnerability/CVE-2025-48749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48749/
Summaries are generated and may contain mistakes; the official description above is the record.