# CVE-2025-48709: BMC Control-M/Server cleartext database credentials in process lists and logs

> An authenticated attacker with shell access can view cleartext database credentials in process lists and logs, allowing unauthorized database access.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-cgj5-r57f-xw42

## What is CVE-2025-48709?

CVE-2025-48709 is a medium-severity vulnerability in BMC Control-M/Server, published on 7 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BMC Control-M/Server 9.0.21.300 displays cleartext database credentials in process lists and logs. An authenticated attacker with shell access could observe these credentials and use them to log in to the database server. For example, when Control-M/Server on Windows has a database connection on, it runs 'DBUStatus.exe' frequently, which then calls 'dbu_connection_details.vbs' with the username, password, database hostname, and port written in cleartext, which can be seen in event and process logs in two separate locations. Fixed in PACTV.9.0.21.307.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-532 (Insertion of Sensitive Information into Log File), CWE-214 (Invocation of Process Using Visible Sensitive Information)

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

It affects 1 product.


Products: Bmc Control-M\/Server.

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

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

## Is CVE-2025-48709 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48709 is a medium-severity vulnerability in BMC Control-M/Server, published on 7 Aug 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-48709 in the wild and no public exploit code.

Affected product: BMC Control-M/Server. 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-48709/ (Markdown: https://insights.sbomify.com/CVE-2025-48709/index.md)
```

## Sources

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

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