Comparison Overview
PowerEmail
PowerEmail
N/A
Last Update: 15/12/2025
With our CRM email tracking add-on, PowerEmail, you can now track whether or not the emails you've sent were opened, and which URLs were clicked on within that email, all, of course, within CRM!
Nagarro
Munich, DE
Last Update: 31/03/2026
Nagarro helps future-proof your business through a forward-thinking, fluidic, and CARING mindset. We excel at digital engineering and help our clients become human-centric, digital-first organizations, augmenting their ability to be responsive, efficient, intimate, crea...
Compliance Ranges Comparison
PowerEmail
Nagarro
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for PowerEmail in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Nagarro in 2026.
Incident History - PowerEmail (X = Date, Y = Severity)
PowerEmail cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nagarro (X = Date, Y = Severity)
Nagarro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PowerEmail
Nagarro
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.