Comparison Overview
Beehive Fintech

Beehive Fintech
Beehive P2P Ltd. , Dubai , UAE, PO Box 506943, AE
Last Update: 19/12/2025
Beehive Fintech, an e& enterprise company,is the first regulated and leading digital SME lending platform in the MENA region. Beehive directly connects smart investors and creditworthy businesses to build mutually beneficial partnerships for growth. Our platform applie...

Discovery Limited
1 Discovery Place, Sandhurst, Johannesburg, Gauteng, ZA, 2196
Last Update: 01/04/2026
Imagine a world where people live healthier, more enhanced and protected lives… A world in which each organisation is a powerful influencer and responsible corporate citizen, committed to being a force for social good. As a leading innovator in healthcare, wellness, ins...
Compliance Ranges Comparison

Beehive Fintech







Discovery Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Beehive Fintech in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Discovery Limited in 2026.
Incident History - Beehive Fintech (X = Date, Y = Severity)
Beehive Fintech cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Discovery Limited (X = Date, Y = Severity)
Discovery Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Beehive Fintech

Discovery Limited
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.