Comparison Overview
Starcom Australia

Starcom Australia
28 Windmill St, Pyrmont, New South Wales, 2009, AU
Last Update: 02/12/2025
With a history that dates back over 80 years, Starcom is a global communications planning and media leader. We are an agency still grounded in our founding principle that people are at the center of all we do. Each day, we apply this belief to harness the transformative...

TBWA\Worldwide
220 E 42nd St, New York, 10017, US
Last Update: 13/09/2026
TBWA is The Disruption Company®. We are a Collective of creative minds with an unlimited creative canvas. We create brand platforms that defy convention and compete with culture. Thanks to our trademarked Disruption® methodology, we build the world’s strongest brands. B...
Compliance Ranges Comparison

Starcom Australia







TBWA\Worldwide






Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Starcom Australia in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for TBWA\Worldwide in 2026.
Incident History - Starcom Australia (X = Date, Y = Severity)
Starcom Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TBWA\Worldwide (X = Date, Y = Severity)
TBWA\Worldwide cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Starcom Australia

TBWA\Worldwide
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)