Comparison Overview
Consolidated High School District 230

Consolidated High School District 230
15100 S. 94th Avenue, Orland Park, 60462, US
Last Update: 04/04/2026
Carl Sandburg High School - 13300 S. LaGrange Road Orland Park, IL 60462 Construction of the first high school in the newly consolidated district began in May, 1953. By September 1954, classes were in session at Carl Sandburg High School at 133rd Street and Route 45 i...

Secretaria de Educação do Estado de Pernambuco
BR
Last Update: 02/04/2026
For 52 years, the Department of Education of Pernambuco was linked to the health department of the State. The disconnect between the two bodies and the consequent acquisition of autonomy of the SE came through Law 466, on 22 April 1949, during the administration of then...
Compliance Ranges Comparison

Consolidated High School District 230







Secretaria de Educação do Estado de Pernambuco






Benchmark & Cyber Underwriting Signals
Incidents vs Education Management Industry Avg (This Year)
No incidents recorded for Consolidated High School District 230 in 2026.
Incidents vs Education Management Industry Avg (This Year)
No incidents recorded for Secretaria de Educação do Estado de Pernambuco in 2026.
Incident History - Consolidated High School District 230 (X = Date, Y = Severity)
Consolidated High School District 230 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Secretaria de Educação do Estado de Pernambuco (X = Date, Y = Severity)
Secretaria de Educação do Estado de Pernambuco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Consolidated High School District 230

Secretaria de Educação do Estado de Pernambuco
FAQ
Latest Global CVEs
Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.
- https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834
- https://github.com/v12-security/pocs/tree/main/redis/server_ssl
- https://raw.githubusercontent.com/redis/redis/8.10/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.2/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.4/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.6/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.8/00-RELEASENOTES
Unrestricted Upload of File with Dangerous Type in the product photo upload in Roskus Prospero Flow CRM before 5.16.0 allows an authenticated user holding the create product permission (routine Seller role) to execute arbitrary JavaScript in the application origin. The photo validation rule classifies the file only by its content (magic bytes) and rejects only a fixed list of PHP extensions, while ProductSaveController::save() names the stored file using the client-supplied extension and copies it into the public web root. A file that begins with an image header and carries an HTML extension passes validation, is stored under public/asset/upload/product/, and is served with a text/html content type, turning the upload into first-party stored script execution.
A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image. Affected version >= 2.26.4
A relative path traversal issue in the zip extraction functionality in AWS diagram-as-code (awsdac) in versions 0.10 through 0.23 can allow a third party to write arbitrary files to the local filesystem via crafted zip entry names containing path traversal sequences. This could allow the third party to perform inappropriate actions in the diagram bundle. To remediate this issue, users should upgrade to the version 0.24 or later.
A weakness has been identified in RooCodeInc Roo-Code up to 3.51.1. Affected by this issue is the function ExecaTerminalProcess of the component README File Handler. Executing a manipulation can lead to code injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.