{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12507 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12507 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12507 is a high-severity vulnerability in Bizerba _connect.BRAIN, published on 31 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12507 and fix it if it is affected.\n\nWhat it is: CVE-2025-12507 is a high-severity vulnerability in Bizerba _connect.BRAIN, published on 31 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12507 in the wild and no public exploit code.\n\nAffected product: Bizerba _connect.BRAIN. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-12507/ (Markdown: https://insights.sbomify.com/CVE-2025-12507/index.md)","id":"CVE-2025-12507","markdown":"https://insights.sbomify.com/CVE-2025-12507/index.md","name":"CVE-2025-12507","record":{"aliases":["GHSA-9cjm-jvqx-xq8q"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bizerba Communication Server","requires_auth":"low_privilege","summary":"Attackers can execute malicious code via unquoted service path in Bizerba Communication Server, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"bizerba","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-428","name":"Unquoted Search Path or Element"}],"description":"The service Bizerba Communication Server (BCS) has an unquoted service path. Due to the way Windows searches the executable for the BCS service, malicious programs can be executed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Insecure service configuration – unquoted path","id":"CVE-2025-12507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Unencrypted communication to Active Directory services","id":"CVE-2025-12508"},"packages":[],"prev":{"headline":"Use of Incorrectly-Resolved Name or Reference in GitLab","id":"CVE-2025-12506"},"products":["_connect.BRAIN"],"published":"2025-10-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-31","vendors":["Bizerba"]},"summary":"Attackers can execute malicious code via unquoted service path in Bizerba Communication Server, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-12507/"}