# CVE-2025-3321: Use of Hard-coded Credentials in OnlineSuite

> An undocumented, non-deactivatable administrative account with hardcoded credentials allows local users to gain elevated privileges on the server.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 6 Jun 2025
- **Updated:** 6 Jun 2025
- **Also known as:** GHSA-4474-w9fw-64jh

## What is CVE-2025-3321?

CVE-2025-3321 is a critical vulnerability in B. Braun Melsungen AG OnlineSuite, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A predefined administrative account is not documented and cannot
be deactivated. This account cannot be misused from the network, only by local
users on the server.

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

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


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

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

## Is CVE-2025-3321 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3321 is a critical vulnerability in B. Braun Melsungen AG OnlineSuite, published on 6 Jun 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-3321 in the wild and no public exploit code.

Affected product: B. Braun Melsungen AG OnlineSuite. 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-3321/ (Markdown: https://insights.sbomify.com/CVE-2025-3321/index.md)
```

## Sources

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

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