Comparison Overview

SAILING Magazine

VS

Fool Church Media

SAILING Magazine

125 E. Main St., Port Washington, Wisconsin, 53074, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.sailingmagazine.net

SAILING Magazine is the oldest continually published sailing magazine in the United States. This large-format magazine covers all aspects of sailing and, with its stunning photography and graphic design, presents it in a way that no other sailing magazine can. In its 50th year of publishing, SAILING is family owned by lifelong sailors. SAILING Magazine prides itself as being a magazine by sailors, for sailors and is a respected voice within the industry.

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

Fool Church Media

4113 Field Stone Ct, Eugene, Or, 97404, US
Last Update: 2025-11-27
Between 750 and 799
http://www.foolchurch.com

We print standard fiction, historical fiction, young adult fiction, science fiction, speculative fiction, fantasy, horror, non-fiction, and the occasional technical book. We are also happy to reprint books that have gone out of print and for which the Author has retained all remaining rights. Short story collections don't sell as well as do novels, so we prefer novels but are willing to accept collections, if they are a part of a combined offer. We will also publish art and movies in the near future.

NAICS: 511
NAICS Definition:
Employees: 2
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/sailingmagazine.jpeg
SAILING Magazine
—
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/fool-church-media.jpeg
Fool Church Media
—
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
SAILING Magazine
100%
Compliance Rate
0/4 Standards Verified
Fool Church Media
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 SAILING Magazine in 2025.

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

No incidents recorded for Fool Church Media in 2025.

Incident History — SAILING Magazine (X = Date, Y = Severity)

SAILING Magazine cyber incidents detection timeline including parent company and subsidiaries

Incident History — Fool Church Media (X = Date, Y = Severity)

Fool Church Media cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sailingmagazine.jpeg
SAILING Magazine
Incidents

No Incident

https://images.rankiteo.com/companyimages/fool-church-media.jpeg
Fool Church Media
Incidents

No Incident

FAQ

Fool Church Media company demonstrates a stronger AI Cybersecurity Score compared to SAILING Magazine company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Fool Church Media company has disclosed a higher number of cyber incidents compared to SAILING Magazine company.

In the current year, Fool Church Media company and SAILING Magazine company have not reported any cyber incidents.

Neither Fool Church Media company nor SAILING Magazine company has reported experiencing a ransomware attack publicly.

Neither Fool Church Media company nor SAILING Magazine company has reported experiencing a data breach publicly.

Neither Fool Church Media company nor SAILING Magazine company has reported experiencing targeted cyberattacks publicly.

Neither SAILING Magazine company nor Fool Church Media company has reported experiencing or disclosing vulnerabilities publicly.

Neither SAILING Magazine nor Fool Church Media holds any compliance certifications.

Neither company holds any compliance certifications.

Neither SAILING Magazine company nor Fool Church Media company has publicly disclosed detailed information about the number of their subsidiaries.

SAILING Magazine company employs more people globally than Fool Church Media company, reflecting its scale as a Book and Periodical Publishing.

Neither SAILING Magazine nor Fool Church Media holds SOC 2 Type 1 certification.

Neither SAILING Magazine nor Fool Church Media holds SOC 2 Type 2 certification.

Neither SAILING Magazine nor Fool Church Media holds ISO 27001 certification.

Neither SAILING Magazine nor Fool Church Media holds PCI DSS certification.

Neither SAILING Magazine nor Fool Church Media holds HIPAA certification.

Neither SAILING Magazine nor Fool Church Media 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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References