Comparison Overview
ZEN3

ZEN3
N/A
Last Update: 30/12/2025
Zen3 Infosolutions is now a wholly-owned subsidiary of Tech Mahindra. We are an AI-first, data-driven, cloud-native organization and work with several leading companies in the world to solve some of their unique challenges. We aim to help our clients lead their industr...

VOIS
London, GB
Last Update: 05/09/2026
VOIS (Vodafone Intelligent Solutions) is a strategic arm of Vodafone Group Plc, creating value for customers by delivering intelligent solutions through Talent, Technology & Transformation. As the largest shared services organisation in the global telco industry, our ...
Compliance Ranges Comparison

ZEN3







VOIS






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

ZEN3

VOIS
FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.