Comparison Overview
San Bernardino City Unified School District

San Bernardino City Unified School District
777 N F St, San Bernardino, California, US, 92410
Last Update: 31/03/2026
The mission of SBCUSD, the leading expert in human learning, is to ensure all students, cradle to career, develop the knowledge, skills, and proficiencies required for college, career, civic, and economic success by inspiring and engaging them in a system distinguished ...

KinderCare Learning Companies
5005 Meadows Rd, Suite 200, Lake Oswego, OR, US, 97035
Last Update: 04/04/2026
Transform lives—including yours—with the nation’s leading provider of early childhood education and child care. We don’t just hold ourselves to the highest standards; we set new ones. Our accredited programs, talented teachers, and research-based curriculum empower chil...
Compliance Ranges Comparison

San Bernardino City Unified School District







KinderCare Learning Companies






Benchmark & Cyber Underwriting Signals
Incidents vs Education Administration Programs Industry Avg (This Year)
No incidents recorded for San Bernardino City Unified School District in 2026.
Incidents vs Education Administration Programs Industry Avg (This Year)
No incidents recorded for KinderCare Learning Companies in 2026.
Incident History - San Bernardino City Unified School District (X = Date, Y = Severity)
San Bernardino City Unified School District cyber incidents detection timeline including parent company and subsidiaries.
Incident History - KinderCare Learning Companies (X = Date, Y = Severity)
KinderCare Learning Companies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

San Bernardino City Unified School District

KinderCare Learning Companies
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.