Comparison Overview
Propark Mobility

Propark Mobility
None, None, Hartford, Connecticut, US, 06103
Last Update: 02/04/2026
Propark Mobility began in 1984 with a 60-space parking lot in Hartford, Conn. Today, the company has expanded to over 1,000 locations in more than 140 cities nationwide. Specializing in parking management, transportation, campus mobility, and electrification services, P...

Lendlease
Level 14, Tower Three, International Towers Sydney, Exchange Place, 300 Barangaroo Ave, Barangaroo, NSW, AU, 2000
Last Update: 14/09/2026
Lendlease is Australia’s leading real estate business with an international investments platform. We’re city shapers, asset creators and trusted partners. Our deep property experience and bold thinking delivers innovative real estate and investment solutions. Very f...
Compliance Ranges Comparison

Propark Mobility







Lendlease






Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Propark Mobility in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Lendlease in 2026.
Incident History - Propark Mobility (X = Date, Y = Severity)
Propark Mobility cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lendlease (X = Date, Y = Severity)
Lendlease cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Propark Mobility

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