Comparison Overview

Concordia Publishing House

VS

Morning

Concordia Publishing House

3557 South Jefferson Avenue, St. Louis, Missouri, 63118, US
Last Update: 2025-11-25
Between 750 and 799

CPH is hiring! Visit cph.org/jobs to apply. Concordia Publishing House is the publishing arm of The Lutheran Church—Missouri Synod. We exist to strengthen and aid member congregations in their proclamation of the Gospel of our Lord Jesus Christ. At Concordia Publishing House we develop, produce, market, and distribute products and services that are faithful to the Scriptures and the Lutheran Confessions. Core product categories include Curriculum, Adult Bible Studies, Vacation Bible School, Youth & Teen Materials, Christian Living Resources, Music Resources, Professional & Academic Resources, Children’s & Adolescent Books, Periodicals, Church Management Software, and Worship Resources. Enjoy this video that demonstrates CPH's mission and vision for the future. http://www.youtube.com/watch?v=Siweo9tiKWU

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

Morning

26 rue Marie Magné, Toulouse, undefined, 31300, FR
Last Update: 2025-11-26
Between 750 and 799

Morning est un éditeur et un distributeur de jeux de société. Depuis nos locaux toulousains, notre équipe dynamique et passionnée met tout en oeuvre pour vous proposer des jeux de qualité : notre équipe Produit se charge de repérer de super prototypes puis de travailler leur mécanique avec leurs auteurs, puis notre département Créa soigne les illustrations et le look de chaque nouveau projet. Après cette étape, les pôles Communication et Commercial entrent en jeu pour promouvoir et distribuer à l'international nos produits, dans les boutiques hyper-spécialisées comme dans les grands magasins.

NAICS: 511
NAICS Definition:
Employees: 4
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/concordia-publishing-house.jpeg
Concordia Publishing House
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/morning-players.jpeg
Morning
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
Concordia Publishing House
100%
Compliance Rate
0/4 Standards Verified
Morning
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 Concordia Publishing House in 2025.

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

No incidents recorded for Morning in 2025.

Incident History — Concordia Publishing House (X = Date, Y = Severity)

Concordia Publishing House cyber incidents detection timeline including parent company and subsidiaries

Incident History — Morning (X = Date, Y = Severity)

Morning cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/concordia-publishing-house.jpeg
Concordia Publishing House
Incidents

No Incident

https://images.rankiteo.com/companyimages/morning-players.jpeg
Morning
Incidents

No Incident

FAQ

Concordia Publishing House company demonstrates a stronger AI Cybersecurity Score compared to Morning company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Morning company has disclosed a higher number of cyber incidents compared to Concordia Publishing House company.

In the current year, Morning company and Concordia Publishing House company have not reported any cyber incidents.

Neither Morning company nor Concordia Publishing House company has reported experiencing a ransomware attack publicly.

Neither Morning company nor Concordia Publishing House company has reported experiencing a data breach publicly.

Neither Morning company nor Concordia Publishing House company has reported experiencing targeted cyberattacks publicly.

Neither Concordia Publishing House company nor Morning company has reported experiencing or disclosing vulnerabilities publicly.

Neither Concordia Publishing House nor Morning holds any compliance certifications.

Neither company holds any compliance certifications.

Concordia Publishing House company has more subsidiaries worldwide compared to Morning company.

Concordia Publishing House company employs more people globally than Morning company, reflecting its scale as a Book and Periodical Publishing.

Neither Concordia Publishing House nor Morning holds SOC 2 Type 1 certification.

Neither Concordia Publishing House nor Morning holds SOC 2 Type 2 certification.

Neither Concordia Publishing House nor Morning holds ISO 27001 certification.

Neither Concordia Publishing House nor Morning holds PCI DSS certification.

Neither Concordia Publishing House nor Morning holds HIPAA certification.

Neither Concordia Publishing House nor Morning 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.