Comparison Overview

MEDHOST

VS

Duke University Health System

MEDHOST

6550 Carothers Parkway, Franklin, TN, 37067, US
Last Update: 2025-11-28
Between 750 and 799

MEDHOST is a provider of market-leading enterprise, departmental and healthcare engagement solutions to healthcare facilities nationwide. Our integrated product portfolio includes intuitive, cloud-based solutions, including YourCareEverywhere, a robust health and wellness consumer engagement platform. Our broad offering of hosting, outsourcing, marketing and consulting services are changing how clinicians and hospital leaders work and collaborate, while generating notable operational improvements. MEDHOST delivers value by enabling hospitals of all types and all sizes to better manage the business of healthcare across the care continuum while meeting evolving regulatory requirements.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 578
Subsidiaries: 3
12-month incidents
0
Known data breaches
1
Attack type number
1

Duke University Health System

2301 Erwin Road, Durham, North Carolina, US, 27710
Last Update: 2025-11-29
Between 750 and 799

As a world-class academic and health care system, Duke Health strives to transform medicine and health locally and globally through innovative scientific research, rapid translation of breakthrough discoveries, educating future clinical and scientific leaders, advocating and practicing evidence-based medicine to improve community health, and leading efforts to eliminate health inequalities.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 11,647
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/medhost.jpeg
MEDHOST
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/duke-university-health-system.jpeg
Duke University Health System
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
MEDHOST
100%
Compliance Rate
0/4 Standards Verified
Duke University Health System
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for MEDHOST in 2025.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Duke University Health System in 2025.

Incident History — MEDHOST (X = Date, Y = Severity)

MEDHOST cyber incidents detection timeline including parent company and subsidiaries

Incident History — Duke University Health System (X = Date, Y = Severity)

Duke University Health System cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/medhost.jpeg
MEDHOST
Incidents

Date Detected: 12/2017
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/duke-university-health-system.jpeg
Duke University Health System
Incidents

No Incident

FAQ

Duke University Health System company demonstrates a stronger AI Cybersecurity Score compared to MEDHOST company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

MEDHOST company has historically faced a number of disclosed cyber incidents, whereas Duke University Health System company has not reported any.

In the current year, Duke University Health System company and MEDHOST company have not reported any cyber incidents.

Neither Duke University Health System company nor MEDHOST company has reported experiencing a ransomware attack publicly.

MEDHOST company has disclosed at least one data breach, while the other Duke University Health System company has not reported such incidents publicly.

Neither Duke University Health System company nor MEDHOST company has reported experiencing targeted cyberattacks publicly.

Neither MEDHOST company nor Duke University Health System company has reported experiencing or disclosing vulnerabilities publicly.

Neither MEDHOST nor Duke University Health System holds any compliance certifications.

Neither company holds any compliance certifications.

MEDHOST company has more subsidiaries worldwide compared to Duke University Health System company.

Duke University Health System company employs more people globally than MEDHOST company, reflecting its scale as a Hospitals and Health Care.

Neither MEDHOST nor Duke University Health System holds SOC 2 Type 1 certification.

Neither MEDHOST nor Duke University Health System holds SOC 2 Type 2 certification.

Neither MEDHOST nor Duke University Health System holds ISO 27001 certification.

Neither MEDHOST nor Duke University Health System holds PCI DSS certification.

Neither MEDHOST nor Duke University Health System holds HIPAA certification.

Neither MEDHOST nor Duke University Health System holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was determined in motogadget mo.lock Ignition Lock up to 20251125. Affected by this vulnerability is an unknown functionality of the component NFC Handler. Executing manipulation can lead to use of hard-coded cryptographic key . The physical device can be targeted for the attack. A high complexity level is associated with this attack. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 1.2
Severity: HIGH
AV:L/AC:H/Au:N/C:P/I:N/A:N
cvss3
Base: 2.0
Severity: HIGH
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
cvss4
Base: 1.0
Severity: HIGH
CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the interview attachment retrieval endpoint in the Recruitment module serves files based solely on an authenticated session and user-supplied identifiers, without verifying whether the requester has permission to access the associated interview record. Because the server does not perform any recruitment-level authorization checks, an ESS-level user with no access to recruitment workflows can directly request interview attachment URLs and receive the corresponding files. This exposes confidential interview documents—including candidate CVs, evaluations, and supporting files—to unauthorized users. The issue arises from relying on predictable object identifiers and session presence rather than validating the user’s association with the relevant recruitment process. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application’s recruitment attachment retrieval endpoint does not enforce the required authorization checks before serving candidate files. Even users restricted to ESS-level access, who have no permission to view the Recruitment module, can directly access candidate attachment URLs. When an authenticated request is made to the attachment endpoint, the system validates the session but does not confirm that the requesting user has the necessary recruitment permissions. As a result, any authenticated user can download CVs and other uploaded documents for arbitrary candidates by issuing direct requests to the attachment endpoint, leading to unauthorized exposure of sensitive applicant data. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application does not invalidate existing sessions when a user is disabled or when a password change occurs, allowing active session cookies to remain valid indefinitely. As a result, a disabled user, or an attacker using a compromised account, can continue to access protected pages and perform operations as long as a prior session remains active. Because the server performs no session revocation or session-store cleanup during these critical state changes, disabling an account or updating credentials has no effect on already-established sessions. This makes administrative disable actions ineffective and allows unauthorized users to retain full access even after an account is closed or a password is reset, exposing the system to prolonged unauthorized use and significantly increasing the impact of account takeover scenarios. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the password reset workflow does not enforce that the username submitted in the final reset request matches the account for which the reset process was originally initiated. After obtaining a valid reset link for any account they can receive email for, an attacker can alter the username parameter in the final reset request to target a different user. Because the system accepts the supplied username without verification, the attacker can set a new password for any chosen account, including privileged accounts, resulting in full account takeover. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X