Comparison Overview

HIGH ON SPORTS

VS

Guest Communications Corporation

HIGH ON SPORTS

None
Last Update: 2025-11-21
Between 750 and 799

We blog, we opine, we love the high that sports has to offer. Covering major international or domestic sports is a job for the biggies (News Corporations and so on), we stick to our expertise the very basic sentiments that encapsulate the world of sports. We are not a sports news site, we are a bunch of sports fanatics who love getting High on Sports and need our regular doses to help ourselves overcome the mundane routines of daily life. We provide the doses for all those addicts in the world who are seeking the better high.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 1
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Guest Communications Corporation

15009 West 101st Terrace, Lenexa, KS, 66215, US
Last Update: 2025-11-27
Between 750 and 799

GCC is a publisher of custom quick reference information directories. The primary features of our product line are quality, durability and update-ability. Founded in 1987, our headquarters is located in a suburb of Kansas City. We also have sales offices in the east and west to better serve our clients. All of our products are produced in our centrally located headquarters facility. This allows us to maintain the highest standards of quality and to respond to our client’s needs, on-time.

NAICS: 511
NAICS Definition:
Employees: 16
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/high-on-sports.jpeg
HIGH ON SPORTS
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/guest-communications-corporation.jpeg
Guest Communications Corporation
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
HIGH ON SPORTS
100%
Compliance Rate
0/4 Standards Verified
Guest Communications Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for HIGH ON SPORTS in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Guest Communications Corporation in 2025.

Incident History — HIGH ON SPORTS (X = Date, Y = Severity)

HIGH ON SPORTS cyber incidents detection timeline including parent company and subsidiaries

Incident History — Guest Communications Corporation (X = Date, Y = Severity)

Guest Communications Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/high-on-sports.jpeg
HIGH ON SPORTS
Incidents

No Incident

https://images.rankiteo.com/companyimages/guest-communications-corporation.jpeg
Guest Communications Corporation
Incidents

No Incident

FAQ

HIGH ON SPORTS company demonstrates a stronger AI Cybersecurity Score compared to Guest Communications Corporation company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Guest Communications Corporation company has disclosed a higher number of cyber incidents compared to HIGH ON SPORTS company.

In the current year, Guest Communications Corporation company and HIGH ON SPORTS company have not reported any cyber incidents.

Neither Guest Communications Corporation company nor HIGH ON SPORTS company has reported experiencing a ransomware attack publicly.

Neither Guest Communications Corporation company nor HIGH ON SPORTS company has reported experiencing a data breach publicly.

Neither Guest Communications Corporation company nor HIGH ON SPORTS company has reported experiencing targeted cyberattacks publicly.

Neither HIGH ON SPORTS company nor Guest Communications Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Neither HIGH ON SPORTS company nor Guest Communications Corporation company has publicly disclosed detailed information about the number of their subsidiaries.

Guest Communications Corporation company employs more people globally than HIGH ON SPORTS company, reflecting its scale as a Book and Periodical Publishing.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds SOC 2 Type 1 certification.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds SOC 2 Type 2 certification.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds ISO 27001 certification.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds PCI DSS certification.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds HIPAA certification.

Neither HIGH ON SPORTS nor Guest Communications Corporation holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.