Comparison Overview
Irritrol Irrigation

Irritrol Irrigation
5825 Jasmine St, Riverside, California, 92504, US
Last Update: 07/05/2026
Irrigation installation can be dirty, difficult and time-consuming. That’s why the professionals choose Irritrol. We stand behind our product like no one else, with a full line of irrigation product. Factor in free domestic call center support and a full line of fully-...

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...
Compliance Ranges Comparison

Irritrol Irrigation







Foxconn






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

Irritrol Irrigation

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