Comparison Overview
Overland Park Regional Medical Center

Overland Park Regional Medical Center
10500 Quivira Rd., Overland Park, 66213, US
Last Update: 31/03/2026
Our hospital serves the community’s healthcare needs by providing compassionate, patient and family-centered care and some of the most advanced treatment options available in the Kansas City region. Overland Park Regional Medical Center has a world-class medical staff w...

WellSpan Health
45 Monument Road, York, 17403, US
Last Update: 03/04/2026
WellSpan Health’s vision is to reimagine healthcare through the delivery of comprehensive, equitable health and wellness solutions throughout our continuum of care. As an integrated delivery system focused on leading in value-based care, we encompass more than 2,500 emp...
Compliance Ranges Comparison

Overland Park Regional Medical Center







WellSpan Health






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

Overland Park Regional Medical Center

WellSpan Health
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.