Comparison Overview
Phreesia

Phreesia
Wilmington, 19803, US
Last Update: 28/08/2026
Phreesia was founded in 2005 to help patients take an active role in their care. Our innovative technology empowers healthcare organizations to better understand their patients and equip them with the knowledge, skills and confidence to succeed. With robust tools for...

Mayo Clinic
200 First St. S.W., Rochester, 55905, US
Last Update: 13/09/2026
Mayo Clinic has expanded and changed in many ways, but our values remain true to the vision of our founders. Our primary value – The needs of the patient come first – guides our plans and decisions as we create the future of health care. Join us and you'll find a cultur...
Compliance Ranges Comparison

Phreesia







Mayo Clinic






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Phreesia in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Mayo Clinic has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Phreesia (X = Date, Y = Severity)
Phreesia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mayo Clinic (X = Date, Y = Severity)
Mayo Clinic cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Phreesia

Mayo Clinic
FAQ
Latest Global CVEs
A vulnerability was identified in Totolink A3002MU Hh-B20211125.1046. Affected is the function formWlEncrypt of the file /boafrm/formWlEncrypt. The manipulation of the argument submit-url leads to buffer overflow. It is possible to initiate the attack remotely. The exploit is publicly available and might be used.
A vulnerability was determined in Totolink A3002MU Hh-B20211125.1046. This impacts the function formWlAc of the file /boafrm/formWlAc. Executing a manipulation of the argument submit-url can lead to buffer overflow. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.
A flaw was found in the OpenShift console. Unauthenticated access to the `/api/devfile/` and `/api/devfile/samples/` endpoints allows a remote attacker to send crafted devfile payloads. This can lead to Server-Side Request Forgery (SSRF), where the console pod makes requests to internal services and reflects partial responses to the attacker. Additionally, by sending repeated large requests without a specified content length, an attacker can cause unbounded memory growth, leading to a Denial of Service (DoS).
In Vinyl Cache before 9.0,2, workspace buffer overflow vulnerability was found in the .upper() and .lower() string type methods of VCL. This can be used as a remote denial of service (DoS) vector to make the child process segfault or assert, and then restart. Effectively exploiting this vulnerability requires prior knowledge about the VCL in use and the ability to craft a request that contains a string that is long enough to fill the remaining workspace at the call site while staying under the different request size limits (http_req_size, http_req_hdr_len, etc.).
A vulnerability was found in Totolink A3002MU Hh-B20211125.1046. This affects the function formSchedule of the file /boafrm/formSchedule. Performing a manipulation of the argument webpage results in buffer overflow. The attack is possible to be carried out remotely. The exploit has been made public and could be used.