Comparison Overview
OpenAir

OpenAir
2955 Campus Dr, San Mateo, CA, US, 94403
Last Update: 18/09/2026
OpenAir started with a simple vision: that project-based organizations needed a more effective way to manage their key assets, namely their employees and their expertise. Just as ERP systems improved manufacturing operations, software could help service firms and intern...

Agoda
20 Cecil Street, #1401, Singapore, 049705, SG
Last Update: 13/09/2026
At Agoda, we bridge the world through travel. We aim to make it easy and rewarding for more travelers to explore and experience the amazing world we live in. We do so by enabling more people to see the world for less – with our best-value deals across our 6,000,000+ hot...
Compliance Ranges Comparison

OpenAir







Agoda






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
OpenAir has 6.54% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
Agoda has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - OpenAir (X = Date, Y = Severity)
OpenAir cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Agoda (X = Date, Y = Severity)
Agoda cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OpenAir

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