Comparison Overview
Pottery Barn Kids

Pottery Barn Kids
151 Union Street, San Francisco, California 94111, US
Last Update: 28/03/2026
Kids are, and have always been, the inspiration behind what we do. Pottery Barn Kids was founded in 1999 by two moms who were designing their kids' bedrooms and couldn't find comfortable, well-made pieces. Since then, it's been our mission to bring the utmost in qualit...

Intermarché
21 allée des Mousquetaires, Bondoufle, 91078, FR
Last Update: 14/09/2026
Reconnue pour son combat contre la vie chère, Intermarché s'appuie sur un réseau de 2 328 points de vente en Europe (France, Belgique, Pologne, Portugal). Spécialiste des produits frais, l’enseigne propose différents formats de points de vente pour répondre aux attentes...
Compliance Ranges Comparison

Pottery Barn Kids







Intermarché






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Pottery Barn Kids in 2026.
Incidents vs Retail Industry Avg (This Year)
Intermarché has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Pottery Barn Kids (X = Date, Y = Severity)
Pottery Barn Kids cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intermarché (X = Date, Y = Severity)
Intermarché cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Pottery Barn Kids

Intermarché
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)