Comparison Overview
Motorola Solutions

Motorola Solutions
500 W. Monroe Street, Chicago, 60661, US
Last Update: 15/09/2026
About Motorola Solutions | Solving for safer Safety and security are at the heart of everything we do at Motorola Solutions. We build and connect technologies to help protect people, property and places. Our solutions foster the collaboration that’s critical for safer ...

Lumen Technologies
Monroe, Louisiana , US, 71203
Last Update: 15/09/2026
Lumen connects the world. We digitally connect people, data and applications – quickly, securely and effortlessly. Everything we do at Lumen takes advantage of our network strength. From metro connectivity to long-haul data transport to our edge cloud, security, and man...
Compliance Ranges Comparison

Motorola Solutions







Lumen Technologies






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

Motorola Solutions

Lumen Technologies
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)