Comparison Overview
Catalyst Brands India

Catalyst Brands India
Manyata Tech Park Road, Bengaluru East, IN
Last Update: 30/10/2025
We are Catalyst Brands. We now bring together the rich heritage of six unique brands, with modern energy and a bold vision for success. Just as a catalyst in science brings together distinct elements to create something greater as a collective, our name ‘Catalyst’ refl...

AS Watson
1-5 Wo Liu Hang Road, Fo Tan, Shatin, Hong Kong, HK
Last Update: 15/09/2026
AS Watson Group, the world’s largest international health and beauty retailer, is operating over 17,000 stores under 12 retail brands in 31 markets, with over 130,000 employees worldwide. For the fiscal year 2024, AS Watson Group recorded revenue of over US$24 billion. ...
Compliance Ranges Comparison

Catalyst Brands India







AS Watson






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Catalyst Brands India in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for AS Watson in 2026.
Incident History - Catalyst Brands India (X = Date, Y = Severity)
Catalyst Brands India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AS Watson (X = Date, Y = Severity)
AS Watson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Catalyst Brands India

AS Watson
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)