Comparison Overview
Sparkasse Bodensee

Sparkasse Bodensee
Charlottenstraße 2, Friedrichshafen, 88045, DE
Last Update: 26/03/2026
Hier entsteht Gutes. Wir sind kein fancy FinTech. Dafür sind wir hier – für euch vor Ort in der Bodensee-Region. Vom ersten Konto über die Finanzierung der eigenen vier Wände bis zur richtigen Altersvorsorge. Hier machen wir uns stark für alles, was wirklich zählt. Im L...

Banco Azteca
Av. Insurgentes Sur 3579, México, 14020, MX
Last Update: 30/04/2026
Banco Azteca es un banco mexicano fundado en el año 2002 y es una compañía de Grupo Salinas del empresario Mexicano Ricardo Salinas Pliego. Cuenta con 1,500 sucursales en México, Panamá, Argentina, Honduras, El Salvador, Brasil y Perú; es uno de los dos bancos más grand...
Compliance Ranges Comparison

Sparkasse Bodensee







Banco Azteca






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

Sparkasse Bodensee

Banco Azteca
FAQ
Latest Global CVEs
VaahCMS versions 2.0.0 through 2.3.4 contain a malicious obfuscated JavaScript payload embedded in the Blade template responsible for rendering security OTP emails, allowing remote attackers to execute unauthorized code in any browser that renders the affected email template with JavaScript enabled. The payload establishes a WebSocket connection to a hardcoded command-and-control endpoint, installs a password-field keylogger using MutationObserver to capture dynamically added inputs, scrapes WhatsApp Web DOM content, and accepts remote commands to redirect or overwrite the rendered page.
undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. Native Blob objects are safe because their constructor strips CRLF from the type, and fetch is unaffected because it validates headers, but ecosystem libraries that build duck-typed blob shapes from user input can reach the vulnerable path. This is the same defect class as CVE-2022-35948 and CVE-2026-1527, on a header sink that the earlier fixes did not cover. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.
undici's cache interceptor mishandles optional whitespace placed around the equals sign of a qualified no-cache or private Cache-Control directive. In undici from 7.0.0 up to before 7.29.0 and from 8.0.0 up to before 8.9.0, the parser either drops the directive or stores a field name with literal quote characters, so the cache decision fails to recognize the qualification and the response is stored. In shared-cache mode, this lets a response containing one user's authenticated data be served from cache to a later caller, including an unauthenticated one, when both requests resolve to the same cache key. It affects applications that enable the cache interceptor in shared mode, forward Authorization headers upstream, and receive cacheable responses with qualified directives padded with whitespace around the equals sign. This is the whitespace-around-equals variant that the fix for CVE-2026-9678 did not normalize, and it is fixed in undici 7.29.0 and 8.9.0.
kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in check_availability.php via the parameters emailid and email.
- https://github.com/um-dsp/TaintRadar/blob/main/sql_injection_cves/hospitalmanagementsystemproject/20250811-hospital-management-system-check_availability.php-email-sqli/20250811-hospital-management-system-check_availability.php-email-sqli.md
- https://github.com/um-dsp/TaintRadar/blob/main/sql_injection_cves/hospitalmanagementsystemproject/20250811-hospital-management-system-check_availability.php-emailid-sqli/20250811-hospital-management-system-check_availability.php-emailid-sqli.md
kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in /doctor/edit-patient.php?editid=1.