CVE-2025-6513
BRAIN2 Configuration file for database access not sufficiently secured
Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
BRAIN2 Configuration file for database access not sufficiently secured
Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.
- Record
CVE-2025-6513- CVSS 3.1
- 9.3 Critical
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-260
- Updated
- 2026-11-02
EUVDEUVD-2025-18871
Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.
- Record
EUVD-2025-18871- CVSS 3.1
- 9.3 Critical
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-7f9h-3v62-fx27
Standard Windows users can access the configuration file for database access of the BRAIN2...
Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.
- Record
GHSA-7f9h-3v62-fx27- CVSS 3.1
- 9.3 Critical
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-260
- Updated
- 2026-11-02
NVD
Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.
- Record
CVE-2025-6513- CVSS 3.1
- 9.3 Critical
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-260
- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-6513 is a critical vulnerability (CVSS 9.3) in Bizerba Brain2, published June 23, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.17%, the 5th percentile. No source names a fixed version.