# CVE-2025-6513: BRAIN2 Configuration file for database access not sufficiently secured

> Standard Windows users can access and decrypt the BRAIN2 database configuration file, exposing sensitive credentials.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A: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:** 23 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-7f9h-3v62-fx27

## What is CVE-2025-6513?

CVE-2025-6513 is a critical vulnerability in Bizerba SE & Co. KG BRAIN2, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.

Weakness: CWE-260 (Password in Configuration File)

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


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

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

## Is CVE-2025-6513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6513 is a critical vulnerability in Bizerba SE & Co. KG BRAIN2, published on 23 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-6513 in the wild and no public exploit code.

Affected product: Bizerba SE & Co. KG BRAIN2. 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-6513/ (Markdown: https://insights.sbomify.com/CVE-2025-6513/index.md)
```

## Sources

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

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