Comparison Overview
Massimo Dutti

Massimo Dutti
Poligono Inditex, Tordera, Barcelona, ES, 08490
Last Update: 04/04/2026
Massimo Dutti (Inditex Group) was founded in 1985 and was acquired by Inditex in 1991. It now has over 700 stores in more than 72 countries. The brand was originally aimed at men's fashion. Starting in 1995, women's fashion was launched in all its dimensions: from the ...

BİM Birleşik Mağazalar A.Ş
Abdurrahmangazi Mah.Ebubekir Cad. No:73 Sancaktepe, İstanbul, TR
Last Update: 06/09/2026
Türkiye’de perakende sektörünün lideri olan BİM Birleşik Mağazalar A.Ş., temel gıda ve tüketim malzemelerinin uygun fiyat ve yüksek kaliteyle tüketiciye ulaştırılması hedefiyle faaliyetlerine 1995 yılında 21 mağazayla başlamıştır. Yüksek indirim (hard-discount) modelini...
Compliance Ranges Comparison

Massimo Dutti







BİM Birleşik Mağazalar A.Ş






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Massimo Dutti in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for BİM Birleşik Mağazalar A.Ş in 2026.
Incident History - Massimo Dutti (X = Date, Y = Severity)
Massimo Dutti cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BİM Birleşik Mağazalar A.Ş (X = Date, Y = Severity)
BİM Birleşik Mağazalar A.Ş cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Massimo Dutti

BİM Birleşik Mağazalar A.Ş
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)