Comparison Overview
Cox Communications

Cox Communications
6205 Peachtree Dunwoody Road, Atlanta, 30328, US
Last Update: 01/04/2026
Cox Communications is committed to creating more moments of real human connection. We bring people closer to family and friends through technology that’s inspired by a culture that puts people first, and we’re always working to improve life in the communities we serve. ...

Globe Telecom
PH
Last Update: 06/09/2026
Globe is a leading full-service telecommunications company in the Philippines and publicly listed in the PSE with the stock symbol GLO. The company serves the telecommunications and technology needs of consumers and businesses across an entire suite of products and serv...
Compliance Ranges Comparison

Cox Communications







Globe Telecom






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Cox Communications in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Globe Telecom in 2026.
Incident History - Cox Communications (X = Date, Y = Severity)
Cox Communications cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Globe Telecom (X = Date, Y = Severity)
Globe Telecom cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Cox Communications

Globe Telecom
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)