Comparison Overview
MasterCorp, Inc.
MasterCorp, Inc.
4700 MILLENIA BLVD, ORLANDO, 32839-6018, US
Last Update: 31/03/2026
With over 45 years of experience, MasterCorp has proudly served as a trusted partner in the hospitality services industry. At the heart of our success is our People Proud culture, where Associates are at the center of every decision we make and the driving force behind ...
Club Med
Paris, FR
Last Update: 04/04/2026
Since it was founded in 1950 and it created the all-inclusive vacation concept, Club Med has been the world leader on its market, and has developed a resolutely upscale, friendly and multicultural spirit. Club Med boasts 70 resorts located in the most beautiful sites in...
Compliance Ranges Comparison
MasterCorp, Inc.
Club Med
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for MasterCorp, Inc. in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Club Med in 2026.
Incident History - MasterCorp, Inc. (X = Date, Y = Severity)
MasterCorp, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Club Med (X = Date, Y = Severity)
Club Med cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MasterCorp, Inc.
Club Med
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.