Comparison Overview
Auckland Law School, University of Auckland

Auckland Law School, University of Auckland
9 Eden Crescent, Auckland, 1010, NZ
Last Update: 08/12/2025
The University of Auckland Law School is committed to improving access to justice for our local, national and global communities through excellence in teaching, research, service and engagement. We have a long tradition of excellence, founded on the calibre of our sta...

Lund University
Lund University, Box 117, Lund, SE, 221 00
Last Update: 02/04/2026
Lund University has around 46 000 students and 8 600 staff based in Lund, Helsingborg and Malmö. We are united in our efforts to understand, explain and improve our world and the human condition. Lund is considered one of the most popular study locations in Sweden. The...
Compliance Ranges Comparison

Auckland Law School, University of Auckland







Lund University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Auckland Law School, University of Auckland in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Lund University in 2026.
Incident History - Auckland Law School, University of Auckland (X = Date, Y = Severity)
Auckland Law School, University of Auckland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lund University (X = Date, Y = Severity)
Lund University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Auckland Law School, University of Auckland

Lund University
FAQ
Latest Global CVEs
A weakness has been identified in PHPGurukul Student Information System 1.0. Affected by this vulnerability is an unknown functionality of the file /student_edit1.php. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.
A vulnerability has been found in macrozheng mall up to 1.0.3. The affected element is an unknown function of the file /order/paySuccess of the component Payment Status Endpoint. The manipulation of the argument orderId leads to enforcement of behavioral workflow. The attack is possible to be carried out remotely. The vendor deleted the GitHub issue for this vulnerability without any explanation.
A security flaw has been discovered in itsourcecode Sales and Inventory System 1.0. Impacted is an unknown function of the file /pages/emp_del.php. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.
A vulnerability was identified in itsourcecode Sales and Inventory System 1.0. This issue affects some unknown processing of the file /pages/emp_edit.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might be used.
The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 2.2.3. This is due to the plugin accepting an attacker-controlled afreg_select_user_role value from the unauthenticated WooCommerce Store API /wc/store/v1/checkout request in the af_reg_checkout_data_to_order_meta_data_block() function, persisting it in order meta, and then passing it directly to WP_User::add_role() in the af_reg_custom_order_processing_function() function (hooked to woocommerce_thankyou) without validating against the plugin's admin-configured allowed role list. This makes it possible for unauthenticated attackers to elevate their privileges to Administrator by creating an account during checkout with a modified JSON body specifying administrator (or any other role slug) as the desired role. Note: The exploit requires the "User Role Selection" setting to be enabled.