Comparison Overview
Propel, now part of Gravita
Propel, now part of Gravita
New Street Square, London, EC4A 3, GB
Last Update: 25/01/2026
We’re excited to announce that on 30th September 2022, Propel was acquired by Gravita Business Services Limited, meaning Propel is now part of the Gravita Group. To explore the services formerly provided by Propel and further information about the Jeffreys Henry Group,...
Baker Tilly US
205 N. Michigan Ave., Chicago, 60601, US
Last Update: 04/04/2026
Baker Tilly is a leading advisory, tax and assurance firm, providing clients with a genuine coast-to-coast and global advantage in major regions of the U.S. and in many of the world’s leading financial centers – New York, London, San Francisco, Seattle, Los Angeles, Chi...
Compliance Ranges Comparison
Propel, now part of Gravita
Baker Tilly US
Benchmark & Cyber Underwriting Signals
Incidents vs Accounting Industry Avg (This Year)
No incidents recorded for Propel, now part of Gravita in 2026.
Incidents vs Accounting Industry Avg (This Year)
No incidents recorded for Baker Tilly US in 2026.
Incident History - Propel, now part of Gravita (X = Date, Y = Severity)
Propel, now part of Gravita cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Baker Tilly US (X = Date, Y = Severity)
Baker Tilly US cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Propel, now part of Gravita
Baker Tilly US
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)