Comparison Overview
XTIUM

XTIUM
New York, NY, US, 10119
Last Update: 04/04/2026
XTIUM, created through the business combination of ATSG and Evolve IP, delivers a modern security-first approach to the managed IT services experience. Leveraging AI innovations, enterprise-grade cybersecurity, virtual desktops, unified communications, and more, XTIUM a...

Mphasis
Mphasis Limited, Bagmane Laurel, 1st Floor, Tower A, , Bagmane Technology Park, C V Raman Nagar, Bangalore, Karnataka, IN, 560093
Last Update: 15/09/2026
A leading applied technology services company, we innovate to deliver service excellence and successful outcomes across sales, delivery and development. With our strategy to be agile, nimble and customer-centric, we anticipate the future of applied technology and predic...
Compliance Ranges Comparison

XTIUM







Mphasis






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
XTIUM has 32.43% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Mphasis in 2026.
Incident History - XTIUM (X = Date, Y = Severity)
XTIUM cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mphasis (X = Date, Y = Severity)
Mphasis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

XTIUM

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