Comparison Overview
IWC Schaffhausen

IWC Schaffhausen
Baumgartenstrasse 15, Schaffhausen, undefined, 8201, CH
Last Update: 27/11/2025
IWC Schaffhausen - Engineering beyond time. A Great Place to Work is where you trust those you work for, where you are proud of what you do and where you enjoy working with others. - Robert Levering, co-founder, Great Place to Work According to the latest employee s...

Christian Dior Couture
30 avenue Montaigne, Paris, 75008, FR
Last Update: 08/05/2026
Welcome to Christian Dior Couture, House of Dreams, House of Talents. Christian Dior was the designer of dreams. In founding his House in 1947, marked by the revolution of the New Look, he metamorphosed his reveries into wonderful creations. His visionary spirit never ...
Compliance Ranges Comparison

IWC Schaffhausen







Christian Dior Couture






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for IWC Schaffhausen in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
Christian Dior Couture has 85.19% more incidents than the average of all companies with at least one recorded incident.
Incident History - IWC Schaffhausen (X = Date, Y = Severity)
IWC Schaffhausen cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Christian Dior Couture (X = Date, Y = Severity)
Christian Dior Couture cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

IWC Schaffhausen

Christian Dior Couture
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.