Comparison Overview
Clark County School District

Clark County School District
Clark County School District, Las Vegas, 89121, US
Last Update: 08/05/2026
The Clark County School District is the 5th largest school district in the nation with over 300,000 students in 357 schools and over 40,000 employees. Our focus is on people – the educators, staff, students and parents who make our community one of the most diverse an...

Jefferson County Public Schools
3332 Newburg Road, Louisville, 40223, US
Last Update: 11/06/2026
— 30th largest school district in the U.S. — 96,000+ students — 17,400+ full- and part-time employees, including 6,800+ certified teachers Vision All JCPS students graduate prepared, empowered, and inspired to reach their full potential and contribute as thoughtful, r...
Compliance Ranges Comparison

Clark County School District







Jefferson County Public Schools






Benchmark & Cyber Underwriting Signals
Incidents vs Education Administration Programs Industry Avg (This Year)
Clark County School District has 45.65% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Education Administration Programs Industry Avg (This Year)
No incidents recorded for Jefferson County Public Schools in 2026.
Incident History - Clark County School District (X = Date, Y = Severity)
Clark County School District cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jefferson County Public Schools (X = Date, Y = Severity)
Jefferson County Public Schools cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Clark County School District

Jefferson County Public Schools
FAQ
Latest Global CVEs
GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.
- https://cgit.git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/file.php?h=release-3.17#n113
- https://cgit.git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/file.php?h=release-3.17#n123
- https://news.ycombinator.com/item?id=48605220
- https://www.fsf.org/news/statement-regarding-gnu-savannah-security-reports
- https://www.hacktron.ai
- https://www.mallory.ai/stories/019ee445-bdd4-7775-93b5-a8faaf5c2eb7
AVideo TopMenu plugin through version 26.0 contains a stored cross-site scripting vulnerability in menu item rendering due to missing output encoding of icon classes, URLs, and text labels. Attackers can inject malicious JavaScript through unescaped menu item fields that execute for all site visitors, potentially stealing session cookies or performing unauthorized actions.
AVideo through version 25.0 contains an authentication bypass vulnerability in the decryptMessage.json.php endpoint that allows unauthenticated users to decrypt PGP messages. Remote attackers can submit private keys, ciphertext, and passphrases to perform server-side decryption without credentials, exposing key material to logs and enabling resource exhaustion attacks.
AVideo through 29.0 contains an authorization bypass vulnerability in the Meet plugin's uploadRecordedVideo.json.php endpoint that derives the target users_id from the uploaded filename without verification. An attacker with knowledge of the Meet shared secret can craft a malicious file upload with a filename containing an arbitrary users_id to invoke passwordless User->login() and establish an authenticated session as any user including admin. Attackers can obtain the Meet shared secret through path-traversal vulnerabilities or timing attacks against checkToken.json.php, then POST a crafted file to uploadRecordedVideo.json.php with a filename like '1-anything.mp4' to hijack admin sessions and gain full account takeover.
AVideo through version 27.0 contains a server-side request forgery vulnerability in plugin/Live/test.php that allows authenticated administrators to read arbitrary URLs via the statsURL parameter, which lacks isSSRFSafeURL() validation and accepts requests to private IP ranges and cloud metadata endpoints. Attackers can exploit this by crafting requests to internal services, cloud metadata endpoints like 169.254.169.254, and localhost to retrieve sensitive information including IAM credentials, internal service responses, and network configuration details.