Comparison Overview

Richland Source

VS

DIS MAGAZINE

Richland Source

40 W 4th Street, Mansfield, 44902, US
Last Update: 2025-11-21
View Profile
Between 750 and 799
https://www.richlandsource.com

Richland Source is a nationally recognized online community news organization founded in 2013. We serve the citizens of North Central Ohio. We are driven by a deeply-held belief that news organizations - especially now - serve their community best when they are involved in it. Readers can support our work by becoming Source Members here: https://www.sourcemembers.com/

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

DIS MAGAZINE

50 Eldridge Street, New York, NY, 10002, US
Last Update: 2025-11-27
Between 750 and 799
http://www.dismagazine.com

DIS is a dissection of fashion, art and commerce which seeks to dissolve conventions, distort realities, disturb ideologies and disrupt the dismal dissemination of fashion discourse. All is open to discussion. There is no final word. DIS does not distinguish between disciplines nor conform to aesthetic value systems. DIS explores the banality and novelty of product and image making. Updated on a constant basis, DIS Magazine is not issue-based: although issues are raised. These include but are not limited to distaste, dystopia, evolved lifestyles, new style options, disco, dysmorphia, and innumerable others. DIS is a collaborative project amongst artists, designers, stylists, writers and friends. We are Lauren Boyle, Solomon Chase, S. Adrian Massey III, Marco Roso, Patrik Sandberg, Nicholas Scholl, and David Toro.

NAICS: 511
NAICS Definition:
Employees: 7
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/richland-source.jpeg
Richland Source
—
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/dis-magazine.jpeg
DIS 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
Compliance Summary
Richland Source
100%
Compliance Rate
0/4 Standards Verified
DIS MAGAZINE
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 Richland Source in 2025.

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

No incidents recorded for DIS MAGAZINE in 2025.

Incident History — Richland Source (X = Date, Y = Severity)

Richland Source cyber incidents detection timeline including parent company and subsidiaries

Incident History — DIS MAGAZINE (X = Date, Y = Severity)

DIS MAGAZINE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/richland-source.jpeg
Richland Source
Incidents

No Incident

https://images.rankiteo.com/companyimages/dis-magazine.jpeg
DIS MAGAZINE
Incidents

No Incident

FAQ

Both Richland Source company and DIS MAGAZINE company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, DIS MAGAZINE company has disclosed a higher number of cyber incidents compared to Richland Source company.

In the current year, DIS MAGAZINE company and Richland Source company have not reported any cyber incidents.

Neither DIS MAGAZINE company nor Richland Source company has reported experiencing a ransomware attack publicly.

Neither DIS MAGAZINE company nor Richland Source company has reported experiencing a data breach publicly.

Neither DIS MAGAZINE company nor Richland Source company has reported experiencing targeted cyberattacks publicly.

Neither Richland Source company nor DIS MAGAZINE company has reported experiencing or disclosing vulnerabilities publicly.

Neither Richland Source nor DIS MAGAZINE holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Richland Source company nor DIS MAGAZINE company has publicly disclosed detailed information about the number of their subsidiaries.

Richland Source company employs more people globally than DIS MAGAZINE company, reflecting its scale as a Book and Periodical Publishing.

Neither Richland Source nor DIS MAGAZINE holds SOC 2 Type 1 certification.

Neither Richland Source nor DIS MAGAZINE holds SOC 2 Type 2 certification.

Neither Richland Source nor DIS MAGAZINE holds ISO 27001 certification.

Neither Richland Source nor DIS MAGAZINE holds PCI DSS certification.

Neither Richland Source nor DIS MAGAZINE holds HIPAA certification.

Neither Richland Source nor DIS MAGAZINE 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