Comparison Overview
Fugro VirGeo®

Fugro VirGeo®
N/A
Last Update: 03/04/2026
Ready to transform the way you manage and share Geo-data? Introducing VirGeo®: our innovative cloud-hosted platform that helps marine and land professionals securely access, share and collaborate on data in real-time, enabling faster decisions, and driving your proje...

Experian
475 Anton Blvd, Costa Mesa, CA, US, 92626
Last Update: 07/09/2026
Experian is a global data and technology company, powering opportunities for people and businesses around the world. We help to redefine lending practices, uncover and prevent fraud, simplify healthcare, deliver digital marketing solutions, and gain deeper insights into...
Compliance Ranges Comparison

Fugro VirGeo®







Experian






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

Fugro VirGeo®

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