Comparison Overview
Moldcell

Moldcell
3 Belgrad Street, Chişinău, undefined, MD-2060, MD
Last Update: 09/03/2026
Moldcell is a part of the CG Cell, the new generation of digital operator. Moldcell is one of the leading telecom operators in the Republic of Moldova providing attractive tariffs, biggest variety of handset offers and affordability of the cutting edge technologies all ...

Rogers Communications
333 Bloor Street East, Toronto, M4W 1G9, CA
Last Update: 11/09/2026
Rogers is Canada’s communications and entertainment company, driven to connect and entertain Canadians. For more information, please visit rogers.com or investors.rogers.com. Déterminée à connecter et à divertir les Canadiens et Canadiennes, Rogers est la référence ...
Compliance Ranges Comparison

Moldcell







Rogers Communications






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Moldcell in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Rogers Communications has 194.12% more incidents than the average of all companies with at least one recorded incident.
Incident History - Moldcell (X = Date, Y = Severity)
Moldcell cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rogers Communications (X = Date, Y = Severity)
Rogers Communications cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Moldcell

Rogers Communications
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)