Comparison Overview
Kreissparkasse Biberach

Kreissparkasse Biberach
27 Zeppelinring, Biberach, 88400, DE
Last Update: 21/03/2026
Wir sind ein regional verankertes Finanzdienstleistungsunternehmen mit Heimatliebe und gehören zu den zehn größten Sparkassen in Baden-Württemberg. Privat- und Firmenkunden bieten wir ein umfängliches Leistungsangebot, welches individuell auf unsere Kundinnen und Kunden...

BAC
Centro Corporativo Plaza Roble, Terrazas B, Piso No. 3. Guachipelín de Escazú., Calle 43 y Aquilino de la Guardia, San José, San José , CR, _
Last Update: 20/09/2026
En BAC, reimaginamos la banca para generar prosperidad en las comunidades que servimos. Estamos comprometidos con la innovación, la sostenibilidad y el desarrollo de soluciones financieras que faciliten la vida de las personas y las empresas. Queremos ser una platafor...
Compliance Ranges Comparison

Kreissparkasse Biberach







BAC






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Kreissparkasse Biberach in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BAC in 2026.
Incident History - Kreissparkasse Biberach (X = Date, Y = Severity)
Kreissparkasse Biberach cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BAC (X = Date, Y = Severity)
BAC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kreissparkasse Biberach

BAC
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)