Comparison Overview
MediFind

MediFind
Baltimore, Philadelphia, Silicon Valley, US
Last Update: 28/08/2026
MediFind is the #1 digital platform for people seeking care across top specialties and thousands of conditions. We use advanced analytics to help families—especially those with serious, chronic and rare diseases—find and connect to the right specialists and treatments f...

McKesson
6555 State Highway 161, Irving, 75039, US
Last Update: 10/09/2026
Welcome to the official LinkedIn page for McKesson Corporation. Our purpose is Advancing Health Outcomes for All®. Guided by a nearly 200-year legacy, we work with biopharma companies, providers, pharmacies, manufacturers, government entities and others to strengthen ...
Compliance Ranges Comparison

MediFind







McKesson






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

MediFind

McKesson
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)