Comparison Overview
University of Toronto Faculty of Law
University of Toronto Faculty of Law
78 Queen's Park, Toronto, ON, M5S 2C5, CA
Last Update: 09/03/2026
The University of Toronto’s Faculty of Law is consistently ranked as the best law school in Canada and among the best in the world. First established in 1887—and for nearly 75 years since the founding of today's modern law school—U of T Law has educated some of the most...
Washington University in St. Louis
One Brookings Drive, St. Louis, mo, US, 63130-4899
Last Update: 24/07/2026
Washington University in St. Louis, a medium-sized, independent university, is dedicated to challenging its faculty and students alike to seek new knowledge and greater understanding of an ever-changing, multicultural world. The university has played an integral role in...
Compliance Ranges Comparison
University of Toronto Faculty of Law
Washington University in St. Louis
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Toronto Faculty of Law in 2026.
Incidents vs Higher Education Industry Avg (This Year)
Washington University in St. Louis has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - University of Toronto Faculty of Law (X = Date, Y = Severity)
University of Toronto Faculty of Law cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Washington University in St. Louis (X = Date, Y = Severity)
Washington University in St. Louis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
University of Toronto Faculty of Law
Washington University in St. Louis
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.