Comparison Overview
Platt Electric Supply

Platt Electric Supply
10605 SW Allen Blvd, Beaverton, OR, 97005, US
Last Update: 12/03/2026
Platt serves customers throughout the west from a network of over 135 full service stocking locations and distribution centers in Salt Lake City, Utah, Beaverton, Oregon, and Patterson, California. Platt is a value-added service company that supplies a broad range of ...

Wesco
225 W Station Square Dr, Pittsburgh, Pennsylvania, US, 15219
Last Update: 12/08/2026
At Wesco, we believe life should run smoothly. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Harnessing 100 years of ingenuity and expertise, we increase profitability...
Compliance Ranges Comparison

Platt Electric Supply







Wesco






Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Platt Electric Supply in 2026.
Incidents vs Wholesale Industry Avg (This Year)
Wesco has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Platt Electric Supply (X = Date, Y = Severity)
Platt Electric Supply cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wesco (X = Date, Y = Severity)
Wesco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Platt Electric Supply

Wesco
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.