Comparison Overview
Foxconn

Foxconn
US
Last Update: 23/09/2026
Established in Taiwan in 1974, Hon Hai Technology Group (Foxconn) (2317: Taiwan) is the world’s largest electronics manufacturer. Foxconn is also the leading technological solution provider, and it continuously leverages its expertise in software and hardware to integra...

Signify
High Tech Campus 48, Eindhoven, North Brabant, NL, 5656 AE
Last Update: 12/09/2026
Signify (Euronext: LIGHT Signify is the world leader in lighting for professionals and consumers. We unlock the extraordinary potential of light for brighter lives and a better world. Our global portfolio of brands deliver advanced products, connected systems and servic...
Compliance Ranges Comparison

Foxconn







Signify






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
Foxconn has 93.24% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Signify in 2026.
Incident History - Foxconn (X = Date, Y = Severity)
Foxconn cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Signify (X = Date, Y = Severity)
Signify cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Foxconn

Signify
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)