Comparison Overview
DanCenter A/S

DanCenter A/S
Lyngbyvej 20, København Ø., undefined, 2100, DK
Last Update: 26/12/2025
DanCenter er en af de største formidlere af ferieboliger i Danmark At være ferieboligformidler vil sige, at vi sørger for at etablere kontakt mellem de udlejere af ferieboliger, som vi har en aftale med, og interesserede lejere til den pågældende feriebolig. Vi ejer ...

Princess Cruises
1510 SE 17th St, Fort Lauderdale, Florida, US, 33316
Last Update: 19/09/2026
Princess is the world’s leading premium cruise line operating a fleet of modern ships visiting over 380 destinations around the globe on more than 160 itineraries. Each moment on Princess is one of wonderful discovery where guests can relax and explore. The choices are ...
Compliance Ranges Comparison

DanCenter A/S







Princess Cruises






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for DanCenter A/S in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
Princess Cruises has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - DanCenter A/S (X = Date, Y = Severity)
DanCenter A/S cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Princess Cruises (X = Date, Y = Severity)
Princess Cruises cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DanCenter A/S

Princess Cruises
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)