Comparison Overview
BNP Paribas Factor Nordics

BNP Paribas Factor Nordics
Adelgade 12, 1, 1123 Copenhagen, Copenhagen, 1123, DK
Last Update: 27/12/2025
"The oxygen in your growth story" The right working capital at the right time. With a customized plan, you get the support you need. We can help you grow your business by: - Pre-financing your invoices, allowing you to maintain good cash flow - Credit insurance against ...

Sparkasse
Friedrichstraße 50, Berlin, 10117, DE
Last Update: 13/09/2026
Sparkassen: Nah, präsent und persönlich Als verlässliche Hausbank stehen wir immer und überall an der Seite unserer Kund:innen und Mitarbeitenden. Mit den Sparkassen können Sie auf exzellente Beratung und einen echten Finanzverbund zählen, der nicht nur Ihre persönliche...
Compliance Ranges Comparison

BNP Paribas Factor Nordics







Sparkasse






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BNP Paribas Factor Nordics in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse in 2026.
Incident History - BNP Paribas Factor Nordics (X = Date, Y = Severity)
BNP Paribas Factor Nordics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sparkasse (X = Date, Y = Severity)
Sparkasse cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BNP Paribas Factor Nordics

Sparkasse
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)