Comparison Overview
WooThemes
WooThemes
US
Last Update: 01/04/2026
Premium themes, plugins & eCommerce for WordPress. What started as 3 WordPress enthusiasts, from 3 different countries, who met online is now an international team of designers, developers and support ninjas supporting millions of sites around the world. Our flagship ...
e&
Abu Dhabi, Abu Dhabi, AE
Last Update: 08/09/2026
We're a global technology group focused on innovation and collaboration to create a better future for all. Since 1976, we've been pioneering new technologies and expanding our reach to more people and places. Today, we provide services to over 163 million customers acro...
Compliance Ranges Comparison
WooThemes
e&
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for WooThemes in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for e& in 2026.
Incident History - WooThemes (X = Date, Y = Severity)
WooThemes cyber incidents detection timeline including parent company and subsidiaries.
Incident History - e& (X = Date, Y = Severity)
e& cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
WooThemes
e&
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.