Comparison Overview
Wetherby Preparatory School

Wetherby Preparatory School
Bryanston Square, London, England, GB
Last Update: 04/04/2026
Wetherby Preparatory School is a prestigious and well-established independent boys’ preparatory in Marylebone, Central London. Our curriculum is carefully crafted to deliver leading preparation for the Common Entrance exams and Scholarships, with outstanding results. A...

Prince George's County Public Schools
14201 School Lane, Upper Marlboro, MD, US, 20772
Last Update: 30/03/2026
Prince George's County Public Schools (PGCPS), one of the nation's 25 largest school districts, has 200 schools and centers, more than 133,000 students and 22,000 employees. The school system serves a diverse student population from urban, suburban and rural communities...
Compliance Ranges Comparison

Wetherby Preparatory School







Prince George's County Public Schools






Benchmark & Cyber Underwriting Signals
Incidents vs Primary and Secondary Education Industry Avg (This Year)
No incidents recorded for Wetherby Preparatory School in 2026.
Incidents vs Primary and Secondary Education Industry Avg (This Year)
No incidents recorded for Prince George's County Public Schools in 2026.
Incident History - Wetherby Preparatory School (X = Date, Y = Severity)
Wetherby Preparatory School cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Prince George's County Public Schools (X = Date, Y = Severity)
Prince George's County Public Schools cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Wetherby Preparatory School

Prince George's County Public Schools
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.