Comparison Overview
Sparkasse Uckermark

Sparkasse Uckermark
Georg-Dreke-Ring 62, Prenzlau, 17291, DE
Last Update: 02/04/2026
May we introduce ourselves? Welcome to Sparkasse Uckermark! Sparkasse Uckermark is one of the public credit institutions with a long tradition, because the savings bank system in the Uckermark district dates back to 1822. Sparkasse Uckermark is more than just an emplo...

Westpac Group
275 Kent St, Sydney, 2000, AU
Last Update: 05/09/2026
From rescue helicopters to signing the Equator Principles, from paying super during parental leave to adding 'Touch ID' biometric technology to our banking apps and being first on the scene with a helping hand in times of crisis... we have a proud history of stepping u...
Compliance Ranges Comparison

Sparkasse Uckermark







Westpac Group






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse Uckermark in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Westpac Group has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Sparkasse Uckermark (X = Date, Y = Severity)
Sparkasse Uckermark cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Westpac Group (X = Date, Y = Severity)
Westpac Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sparkasse Uckermark

Westpac Group
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)