Comparison Overview

Daye

VS

MedShare

Daye

The Biscuit Factory , Southwark, London, SE16 4DG, GB
Last Update: 2025-11-28
View Profile
Between 750 and 799
http://www.yourdaye.com

Daye is a female-founded gynae health start-up on a mission to close the gender health gap for good. We started out with the invention of the world’s first pain-relieving tampon, designed to support the 90% of women who experience menstrual cramps. After helping over 75,000 women & AFAB individuals kick period pain to the curb, we launched our second generation tampon to facilitate the at-home detection of vaginal infections, STIs and HPV. Next, we want to develop solutions for under-served gynae health conditions like endometriosis, PCOS and menopause. Within the next five years, we will build an ecosystem where every woman can understand, monitor, and improve her health from her smartphone.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 97
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

MedShare

3240 Clifton Springs Rd, Decatur, GA, 30034, US
Last Update: 2025-11-28
Between 750 and 799
http://www.medshare.org

MedShare is a 501c(3) humanitarian aid organization dedicated to improving the quality of life of people, communities and our planet by sourcing and directly delivering surplus medical supplies and equipment to medically vulnerable communities in the U.S. and around the world. MedShare helps increase health system capacity and drives sustainability by providing biomedical equipment training and service to healthcare organizations and medical professionals serving populations in need. MedShare’s deliveries of vital medical supplies and equipment have decreased our nation’s carbon footprint and brought health, healing and the promise of better lives to 100 countries and countless patients.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 57
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/yourdaye.jpeg
Daye
—
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/medshare_306381.jpeg
MedShare
—
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
Daye
100%
Compliance Rate
0/4 Standards Verified
MedShare
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Daye in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for MedShare in 2025.

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

Daye cyber incidents detection timeline including parent company and subsidiaries

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

MedShare cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/yourdaye.jpeg
Daye
Incidents

No Incident

https://images.rankiteo.com/companyimages/medshare_306381.jpeg
MedShare
Incidents

No Incident

FAQ

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

Historically, MedShare company has disclosed a higher number of cyber incidents compared to Daye company.

In the current year, MedShare company and Daye company have not reported any cyber incidents.

Neither MedShare company nor Daye company has reported experiencing a ransomware attack publicly.

Neither MedShare company nor Daye company has reported experiencing a data breach publicly.

Neither MedShare company nor Daye company has reported experiencing targeted cyberattacks publicly.

Neither Daye company nor MedShare company has reported experiencing or disclosing vulnerabilities publicly.

Neither Daye nor MedShare holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Daye company nor MedShare company has publicly disclosed detailed information about the number of their subsidiaries.

Daye company employs more people globally than MedShare company, reflecting its scale as a Public Health.

Neither Daye nor MedShare holds SOC 2 Type 1 certification.

Neither Daye nor MedShare holds SOC 2 Type 2 certification.

Neither Daye nor MedShare holds ISO 27001 certification.

Neither Daye nor MedShare holds PCI DSS certification.

Neither Daye nor MedShare holds HIPAA certification.

Neither Daye nor MedShare holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/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
References
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
References
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References