Comparison Overview
Agilent Technologies

Agilent Technologies
5301 Stevens Creek Boulevard, Santa Clara, 95051, US
Last Update: 01/04/2026
Agilent customers are finding new ways to treat cancer, ensure food, water, air, and medicine quality and safety, discover new drug treatments, research infectious diseases, and create alternative energy solutions for a greener planet. From start to finish, we have them...

Amgen
One Amgen Center Drive, Thousand Oaks, 91320, US
Last Update: 24/08/2026
Amgen harnesses the best of biology and technology to fight the world’s toughest diseases, and make people’s lives easier, fuller and longer. We helped establish the biotechnology industry, and we remain on the cutting-edge of innovation, using technology and human gene...
Compliance Ranges Comparison

Agilent Technologies







Amgen






Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Agilent Technologies in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
Amgen has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Agilent Technologies (X = Date, Y = Severity)
Agilent Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amgen (X = Date, Y = Severity)
Amgen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Agilent Technologies

Amgen
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.