Comparison Overview
Mobext - Philippines

Mobext - Philippines
4th Floor Executive Building, 369 Jupiter St., Makati City, Makati, National Capital Region, 1209, PH
Last Update: 01/11/2025
Mobext Philippines is an award-winning, mobile-first, creative digital agency. Our mission is to transform our clients' businesses through mobile-first, creative digital solutions. Mobext Philippines is a subsidiary of the Havas Group, one of the world's largest ad...

VML
3 WTC 175 Greenwich Street, New York, New York, US
Last Update: 15/09/2026
VML is a global powerhouse born from the unification of Wunderman Thompson and VMLY&R — two of the world's most powerful and accomplished creative agencies with complementary capabilities and geographic strengths. We have an industry-unique opportunity to provide our cl...
Compliance Ranges Comparison

Mobext - Philippines







VML






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

Mobext - Philippines

VML
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)