Comparison Overview
OpenText Content Cloud

OpenText Content Cloud
275 Frank Tompa Dr, Waterloo, N2L 0A1, CA
Last Update: 11/02/2026
Meet your teams where they are already working with OpenText™ Content Cloud, a composable platform that connects people, content and process to power employee productivity and smarter, faster decisions. Stop information chaos with integrated business processes and secur...

Xiaomi Technology
No. 33 Xi erqi Middle Road, Haidian District, Beijing,100085,China, Beijing, CN
Last Update: 21/09/2026
Xiaomi Corporation was founded in April 2010 and listed on the Main Board of the Hong Kong Stock Exchange on July 9, 2018 (1810.HK). Xiaomi is a consumer electronics and smart manufacturing company with smartphones and smart hardware connected by an IoT platform at its ...
Compliance Ranges Comparison

OpenText Content Cloud







Xiaomi Technology






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for OpenText Content Cloud in 2026.
Incidents vs Software Development Industry Avg (This Year)
Xiaomi Technology has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - OpenText Content Cloud (X = Date, Y = Severity)
OpenText Content Cloud cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Xiaomi Technology (X = Date, Y = Severity)
Xiaomi Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OpenText Content Cloud

Xiaomi Technology
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)