Comparison Overview
El Super
El Super
14601B Lakewood Blvd, Paramount, CA, 90723, US
Last Update: 29/04/2026
Bodega Latina Corporation, doing business as El Super, entered the grocery retail marketplace with its first store in South Gate, California in June of 1997. Headquartered in Paramount, California, El Super is focused on offering the communities we serve exceptional ser...
Coop
Thiersteinerallee 14, Basel, 4002, CH
Last Update: 04/04/2026
Coop has been an integral part of Switzerland for over 150 years and acts with a sense of responsibility for its people, its regions and its ecosystems. As a retailer, wholesaler and producer, we deliver quality and are proud of our numerous brands and products. The div...
Compliance Ranges Comparison
El Super
Coop
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for El Super in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Coop in 2026.
Incident History - El Super (X = Date, Y = Severity)
El Super cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coop (X = Date, Y = Severity)
Coop cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
El Super
Coop
FAQ
Latest Global CVEs
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.
UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.