Comparison Overview

OpenEMR

VS

YouTube

OpenEMR

Last Update: 2025-12-17
Between 750 and 799

The OpenEMR Foundation supports OpenEMR, an open-source electronic medical records software that is used all around the globe. We strive to improve the health care delivery system globally by providing low-cost solutions to clinics big and small. Our international users benefit from a royalty-free license with affordable infrastructure solutions available via both Google Cloud and Amazon Web Services.

NAICS: 513
NAICS Definition: Others
Employees: 2
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

YouTube

901 Cherry Ave., San Bruno, CA, US, 94066
Last Update: 2025-12-16
Between 800 and 849

YouTube is a team-oriented, creative workplace where every single employee has a voice in the choices we make and the features we implement. We work together in small teams to design, develop, and roll out key features and products in very short time frames. Which means something you write today could be seen by millions of viewers tomorrow. And even though we’re a part of Google and enjoy all of the corporate perks, it still feels like you’re working at a startup. YouTube is headquartered in San Bruno, California, 12 miles south of San Francisco. We also have many job openings in Mountain View, and across the globe

NAICS: 513
NAICS Definition: Others
Employees: 140,477
Subsidiaries: 46
12-month incidents
0
Known data breaches
4
Attack type number
5

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/openemr.jpeg
OpenEMR
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/youtube.jpeg
YouTube
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
OpenEMR
100%
Compliance Rate
0/4 Standards Verified
YouTube
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Technology, Information and Internet Industry Average (This Year)

No incidents recorded for OpenEMR in 2025.

Incidents vs Technology, Information and Internet Industry Average (This Year)

No incidents recorded for YouTube in 2025.

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

OpenEMR cyber incidents detection timeline including parent company and subsidiaries

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

YouTube cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/openemr.jpeg
OpenEMR
Incidents

Date Detected: 2/2023
Type:Vulnerability
Attack Vector: Unauthenticated File Read, Authenticated Local File Inclusion, Authenticated Reflected XSS
Motivation: Data breach, ransomware attacks
Blog: Blog
https://images.rankiteo.com/companyimages/youtube.jpeg
YouTube
Incidents

Date Detected: 12/2025
Type:Vulnerability
Attack Vector: Email processing systems, Calendar invitation structures, Document files
Blog: Blog

Date Detected: 8/2025
Type:Cyber Attack
Attack Vector: Email Spoofing, Messaging Platform (WhatsApp)
Motivation: Financial Gain (Fraudulent Services/Products) or Data Theft
Blog: Blog

Date Detected: 7/2025
Type:Vulnerability
Attack Vector: Prompt-injection technique through crafted HTML and CSS code
Motivation: Credential theft, social engineering
Blog: Blog

FAQ

YouTube company demonstrates a stronger AI Cybersecurity Score compared to OpenEMR company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

YouTube company has faced a higher number of disclosed cyber incidents historically compared to OpenEMR company.

In the current year, YouTube company has reported more cyber incidents than OpenEMR company.

YouTube company has confirmed experiencing a ransomware attack, while OpenEMR company has not reported such incidents publicly.

YouTube company has disclosed at least one data breach, while OpenEMR company has not reported such incidents publicly.

YouTube company has reported targeted cyberattacks, while OpenEMR company has not reported such incidents publicly.

Both OpenEMR company and YouTube company have disclosed vulnerabilities.

Neither OpenEMR nor YouTube holds any compliance certifications.

Neither company holds any compliance certifications.

YouTube company has more subsidiaries worldwide compared to OpenEMR company.

YouTube company employs more people globally than OpenEMR company, reflecting its scale as a Technology, Information and Internet.

Neither OpenEMR nor YouTube holds SOC 2 Type 1 certification.

Neither OpenEMR nor YouTube holds SOC 2 Type 2 certification.

Neither OpenEMR nor YouTube holds ISO 27001 certification.

Neither OpenEMR nor YouTube holds PCI DSS certification.

Neither OpenEMR nor YouTube holds HIPAA certification.

Neither OpenEMR nor YouTube holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \~1 hour, the victim’s browser will complete the flow. This leads to login CSRF. Depending on the app’s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue.

Risk Information
cvss3
Base: 5.9
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
Description

FileZilla Client 3.63.1 contains a DLL hijacking vulnerability that allows attackers to execute malicious code by placing a crafted TextShaping.dll in the application directory. Attackers can generate a reverse shell payload using msfvenom and replace the missing DLL to achieve remote code execution when the application launches.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/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

LDAP Tool Box Self Service Password 1.5.2 contains a password reset vulnerability that allows attackers to manipulate HTTP Host headers during token generation. Attackers can craft malicious password reset requests that generate tokens sent to a controlled server, enabling potential account takeover by intercepting and using stolen reset tokens.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/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

Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. Attackers can trick victims into executing a crafted PHP script that captures and writes session cookie information to a file, enabling potential session hijacking.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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