Comparison Overview
CCleaner

CCleaner
London, GB
Last Update: 12/08/2026
CCleaner is part of Gen™ (NASDAQ: GEN), a global company dedicated to powering Digital Freedom with a family of trusted consumer brands.

Coforge
Noida Expressway, Noida, 201304, IN
Last Update: 03/09/2026
Coforge is a global digital services and solutions provider that fuses deep domain expertise with emerging technologies to deliver real-world business impact. With a sharp focus on select industries and an execution intensity that’s uniquely our own, Coforge has emerge...
Compliance Ranges Comparison

CCleaner







Coforge






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
CCleaner has 31.51% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Coforge in 2026.
Incident History - CCleaner (X = Date, Y = Severity)
CCleaner cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coforge (X = Date, Y = Severity)
Coforge cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CCleaner

Coforge
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.