Comparison Overview
MACRO, A Savills Company

MACRO, A Savills Company
399 Park Ave, New York, 10022, US
Last Update: 19/03/2026
Five years ago, Macro joined Savills with the goal of bringing best-in-class project management into a global platform and we are proud to be part of the Savills family. As we mark this milestone, we want to give our community one place to find us. Going forward, all u...

EY-Parthenon
1 More London Place, London, SE1 2AF, GB
Last Update: 29/03/2026
Our unique combination of transformative strategy, transactions and corporate finance delivers real-world value – solutions that work in practice, not just on paper. Benefiting from EY’s full spectrum of services, we’ve reimagined strategic consulting to work in a worl...
Compliance Ranges Comparison

MACRO, A Savills Company







EY-Parthenon






Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for MACRO, A Savills Company in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for EY-Parthenon in 2026.
Incident History - MACRO, A Savills Company (X = Date, Y = Severity)
MACRO, A Savills Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EY-Parthenon (X = Date, Y = Severity)
EY-Parthenon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MACRO, A Savills Company

EY-Parthenon
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)