Comparison Overview
Moses/Weitzman Health System

Moses/Weitzman Health System
N/A
Last Update: 31/03/2026
The Moses/Weitzman Health System is a global leader addressing challenges faced by organizations caring for the poor and diverse populations, and is home to programs focusing on education, research, and process improvement support for safety net providers. The system de...

WVU Medicine
1 Medical Center Dr, Morgantown, 26506, US
Last Update: 03/12/2025
The West Virginia University Health System, which operates under the brand WVU Medicine, is West Virginia’s largest health system and the state’s largest employer with more than 3,400 licensed beds, 4,600 providers, 35,000 employees, and $7 billion in total operating re...
Compliance Ranges Comparison

Moses/Weitzman Health System







WVU Medicine






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Moses/Weitzman Health System in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for WVU Medicine in 2026.
Incident History - Moses/Weitzman Health System (X = Date, Y = Severity)
Moses/Weitzman Health System cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WVU Medicine (X = Date, Y = Severity)
WVU Medicine cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Moses/Weitzman Health System

WVU Medicine
FAQ
Latest Global CVEs
ntop nDPI versions before 6.0 contain a heap buffer overflow vulnerability in the ndpi_json_string_escape function that writes beyond caller-supplied buffer boundaries. Attackers can trigger the overflow by supplying crafted network packet data including TLS SNI, HTTP headers, or DNS names that reach the vulnerable function, causing heap corruption.
PX4 Autopilot through 1.17.0 contains a null pointer dereference vulnerability in param_set_default_file() and param_set_backup_file() functions that allows attackers to crash the autopilot process. Attackers can invoke 'param select' or 'param select-backup' commands with no path argument from any PX4 shell to trigger the crash.
- https://github.com/PX4/PX4-Autopilot
- https://github.com/PX4/PX4-Autopilot/blob/v1.17.0/src/lib/parameters/parameters.cpp
- https://github.com/PX4/PX4-Autopilot/commit/02eabc08c9b8cb1de525070cacb7ea0c495136f6
- https://github.com/PX4/PX4-Autopilot/pull/28475
- https://www.vulncheck.com/advisories/px4-autopilot-through-1.17.0-null-pointer-dereference-via-param-select
PX4 Autopilot through 1.17.0 contains a use-after-free vulnerability in TemperatureCalibration::start() due to a race condition between task spawning and object deletion. Attackers can trigger the calibration process via shell commands to write to freed heap memory, corrupting unrelated objects or allocator metadata and destabilizing heap operations.
- https://github.com/PX4/PX4-Autopilot
- https://github.com/PX4/PX4-Autopilot/blob/v1.17.0/src/modules/temperature_compensation/temperature_calibration/task.cpp
- https://github.com/PX4/PX4-Autopilot/commit/b182e523d154fe029a49b48bb5f9d3d6693bc6bb
- https://github.com/PX4/PX4-Autopilot/pull/28487
- https://www.vulncheck.com/advisories/px4-autopilot-through-1.17.0-use-after-free-via-temperature-calibration-task-startup
Unidata netcdf-c through 4.10.1 contains an out-of-bounds write vulnerability in NC4_HDF5_inq_attname() that copies HDF5 attribute names into a fixed 256-byte buffer without length validation. Attackers can craft HDF5 files with oversized attribute names to overflow the destination buffer, causing memory corruption and crashes when applications enumerate attribute names.
Laravel is a web application framework. Prior to versions 12.60.0 and 13.10.0, a CRLF injection vulnerability in Laravel's email validation, in combination with how Symfony Mailer and Symfony Mime handle certain character sequences, may allow an unauthenticated attacker to interfere with outbound email processing in applications that send mail to user-supplied addresses. This issue has been patched in versions 12.60.0 and 13.10.0.
- https://github.com/laravel/framework/commit/96e9a663db657cf37ef26cd794fda8ff60eaa451
- https://github.com/laravel/framework/commit/f336ba79e744257f84ebf0d096b0ebc62e8e1a4d
- https://github.com/laravel/framework/pull/60151
- https://github.com/laravel/framework/releases/tag/v12.60.0
- https://github.com/laravel/framework/releases/tag/v13.10.0
- https://github.com/laravel/framework/security/advisories/GHSA-5vg9-5847-vvmq