Skip to main content
VulnerabilityPublished Updated

CVE-2025-48709: BMC Control-M · CWE-214

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-48709· Medium 4.8

Not known to be exploited · CVSS 4.8 Medium.

Data as of 21 Nov 2026, 03:45 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisa-cg)CVSS 4.04.8
CNA (cisa-cg)CVSS 3.13.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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

AI-suggested

Since the vulnerability involves exposure of credentials in logs, organizations should restrict access to logs and monitor for unauthorized access. Check with BMC for any forthcoming patches or advisories addressing this issue.

Description

BMC Control-M 9.0.21.300 contains a vulnerability where sensitive database credentials are exposed in cleartext within event and process logs. This occurs because the Control-M Server frequently runs DBUStatus.exe, which calls a script passing the username, password, hostname, and port in plaintext. This exposure can lead to credential compromise.

References

Community reviews

Loading reviews…