Comparison Overview
Wharton Executive Education | CTO Program

Wharton Executive Education | CTO Program
undefined, Philadelphia, undefined, undefined, US
Last Update: 18/04/2026
Wharton Executive Education’s Chief Technology Officer (CTO) Program will help senior technology professionals like you navigate an unpredictable terrain with confidence and equip you with the multifaceted knowledge you need to emerge as a leader who can orchestrate tec...

Washington State University
Pullman/Spokane/Tri-Cities/Vancouver/Everett/Global, Pullman/Spokane/Tri-Cities/Vancouver/Everett/Global, Washington, US, 99164
Last Update: 01/04/2026
Washington State University is a nationally recognized land-grant research university, founded in Pullman in 1890. WSU’s statewide system includes campuses in Pullman, Spokane, Everett, Tri-Cities and Vancouver, with extension and research offices in every county of the...
Compliance Ranges Comparison

Wharton Executive Education | CTO Program







Washington State University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Wharton Executive Education | CTO Program in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Washington State University in 2026.
Incident History - Wharton Executive Education | CTO Program (X = Date, Y = Severity)
Wharton Executive Education | CTO Program cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Washington State University (X = Date, Y = Severity)
Washington State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Wharton Executive Education | CTO Program

Washington State University
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.