Comparison Overview
Havas B2B

Havas B2B
29-30, Quai de Dion Bouton, Puteaux, 92800, FR
Last Update: 30/03/2026
Chez Havas Paris, nous plaçons la marque meaningful au centre du B2B. Dans le monde de l’entreprise, elle est un véritable atout business : elle agit comme un repère stratégique, fédère des communautés, attire les talents et accélère la performance. Notre approche s’a...

Publicis Sapient
40 Water St, Boston, 02109, US
Last Update: 13/09/2026
Publicis Sapient is a technology company that provides enterprise AI platforms and services. With over 30 years of digital business transformation experience, we enable enterprise clients to transform how they operate and serve their customers, unlocking new value and e...
Compliance Ranges Comparison

Havas B2B







Publicis Sapient






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

Havas B2B

Publicis Sapient
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)