Comparison Overview
Sedgebrook

Sedgebrook
800 Audubon Way, Lincolnshire, 60069, US
Last Update: 31/03/2026
Join a community that’s passionate about caring. If you’re passionate about caring and committed to doing your best every day, Sedgebrook may be the place for you. Our community boasts a high degree of resident and staff satisfaction, and we’re looking for people who a...

University of Maryland Medical System
22 S. Greene St, Baltimore, MD, US, 21201
Last Update: 10/09/2026
The University of Maryland Medical System (UMMS) was created in 1984 when the state-owned University Hospital became a private, nonprofit organization. It has evolved into a multi-hospital system with academic, community and specialty service missions reaching every par...
Compliance Ranges Comparison

Sedgebrook







University of Maryland Medical System






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sedgebrook in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for University of Maryland Medical System in 2026.
Incident History - Sedgebrook (X = Date, Y = Severity)
Sedgebrook cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Maryland Medical System (X = Date, Y = Severity)
University of Maryland Medical System cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sedgebrook

University of Maryland Medical System
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)