Comparison Overview
Stylight
Stylight
N/A
Last Update: 19/03/2026
What is Stylight? Founded in 2008, Stylight is the leading aggregation platform for the fashion and lifestyle industry worldwide. We help our 90 million yearly shoppers in 11 countries worldwide search more than 1,000 online shops at once, compare prices of more than 5...
Tieto
N/A
Last Update: 19/09/2026
Tieto provides customers across different industries with mission-critical solutions through its specialized software businesses Tieto Caretech, Tieto Banktech and Tieto Indtech as well as Tieto Tech Consulting business. The company's around 13 000 talented vertical sof...
Compliance Ranges Comparison
Stylight
Tieto
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Stylight in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Tieto in 2026.
Incident History - Stylight (X = Date, Y = Severity)
Stylight cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tieto (X = Date, Y = Severity)
Tieto cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Stylight
Tieto
FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.