Skip to main content
CVE-2025-6512VulnerabilityPublished

CVE-2025-6512: Bizerba SE & Co. KG BRAIN2 · Code Injection

Affects Bizerba SE & Co. KG BRAIN2Source CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Bizerba SE & Co. KG BRAIN2Affected
  • =0.0
Fixed in–

AI-suggested

1. Immediate isolation of BRAIN2 servers from untrusted networks to reduce exposure until a patch is available. 2. Implement strict network segmentation and firewall rules to limit access to BRAIN2 management interfaces only to trusted administrators and systems. 3. Monitor logs and reports generated by BRAIN2 for unusual or unexpected script content or execution patterns. 4. Employ application-layer intrusion detection systems (IDS) to detect anomalous code injection attempts in report submissions. 5. Enforce strict input validation and sanitization on report generation interfaces, if possible, through custom controls or intermediary validation proxies. 6. Coordinate with Bizerba for timely updates and patches; apply them immediately once released. 7. Conduct security awareness training for users interacting with BRAIN2 to recognize suspicious activities. 8. Consider deploying endpoint detection and response (EDR) solutions on servers hosting BRAIN2 to detect and respond to suspicious code execution. 9. Review and restrict user permissions on client systems to minimize the ability to create or modify reports with embedded scripts. 10. Establish incident response plans specifically addressing potential exploitation of this vulnerability.

Description

On a client with a non-admin user, a script can be integrated into a report. The reports could later be executed on the BRAIN2 server with administrator rights.

References

Community reviews

Loading reviews…