# CVE-2025-58385: Hardcoded credentials in n/a

> Attackers can disclose private user PUK codes for Active Directory users due to hard-coded and predictable data in DOXENSE WATCHDOC.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-vhcj-c9x4-2fgg

## What is CVE-2025-58385?

CVE-2025-58385 is a high-severity vulnerability in n/a, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In DOXENSE WATCHDOC before 6.1.0.5094, private user puk codes can be disclosed for Active Directory registered users (there is hard-coded and predictable data).

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Doxense Watchdoc.

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

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

## Is CVE-2025-58385 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58385 is a high-severity vulnerability in n/a, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58385 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-58385/ (Markdown: https://insights.sbomify.com/CVE-2025-58385/index.md)
```

## Sources

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

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