Comparison Overview
Hallmark Cards
Hallmark Cards
2501 McGee, Kansas City, 64108, US
Last Update: 11/09/2026
Hallmark believes if you care enough you can change the world as we work to help create a more emotionally connected world in every life, every day. Founded in 1910 by a teenage entrepreneur with two shoe boxes of postcards under his arm, Hallmark today is still famil...
Pilot Flying J
5508 Lonas Rd., Knoxville, 37909, US
Last Update: 05/09/2026
Company Overview Headquartered in Knoxville, Tennessee, Pilot Flying J is the largest operator of travel centers in North America with more than 750 locations throughout the United States and Canada and employs more than 24,000 Team Members. Pilot Flying J services over...
Compliance Ranges Comparison
Hallmark Cards
Pilot Flying J
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
Hallmark Cards has 63.04% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Pilot Flying J in 2026.
Incident History - Hallmark Cards (X = Date, Y = Severity)
Hallmark Cards cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pilot Flying J (X = Date, Y = Severity)
Pilot Flying J cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hallmark Cards
Pilot Flying J
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)