Comparison Overview

Uitgeverij Podium

VS

Verbum

Uitgeverij Podium

Amsterdam, NL
Last Update: 2025-11-21
View Profile
Between 800 and 849
http://www.uitgeverijpodium.nl

Uitgeverij Podium werd in 1997 opgericht door Joost Nijsen, mede mogelijk gemaakt door de loyaliteit van Nederlandse auteurs die hij eerder uitgaf bij Nijgh & Van Ditmar en Balans, zoals Herman Franke, Ronald Giphart, Nicolaas Klei, Manon Uphoff en Henk van Woerden. Podium is vanaf de oprichting een zelfstandige uitgeverij, gespecialiseerd in hedendaagse Nederlandse en vertaalde literatuur (proza, poëzie) en literaire en journalistieke non-fictie. Dankzij een selectieve fondsvorming en beheerste titelproductie, kan door het enthousiaste en deskundige team aan de uitgegeven titels veel zorg worden besteed, zowel aan redactie en productie als aan verkoop en marketing.

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

Verbum

Kungsholmstorg 5, Stockholm, 112 21, SE
Last Update: 2025-11-28
Between 750 and 799
https://www.verbum.se

Verbum stödjer församlingar med produkter och tjänster som gör skillnad. Vi levererar inspirerande och engagerande lösningar med djup insikt i församlingarnas unika behov. Genom utbildning, böcker, tidningar och digitala- och konsulterande tjänster som underlättar i det dagliga arbetet hjälper vi församlingar att växa och nå sina visioner. Med stark kyrklig förankring och gedigen kunskap om församlingarnas behov är vi en relevant partner. Verbum ägs av bland annat Svenska kyrkan, Equmeniakyrkan och Svenska kyrkans arbetsgivarorganisation och är en del av Berling Media AB. I Verbum ingår också Kyrkans Tidning och Votum Media.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 29
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/uitgeverij-podium.jpeg
Uitgeverij Podium
—
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/verbum-ab.jpeg
Verbum
—
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
Uitgeverij Podium
100%
Compliance Rate
0/4 Standards Verified
Verbum
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 Uitgeverij Podium in 2025.

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

No incidents recorded for Verbum in 2025.

Incident History — Uitgeverij Podium (X = Date, Y = Severity)

Uitgeverij Podium cyber incidents detection timeline including parent company and subsidiaries

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

Verbum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/uitgeverij-podium.jpeg
Uitgeverij Podium
Incidents

No Incident

https://images.rankiteo.com/companyimages/verbum-ab.jpeg
Verbum
Incidents

No Incident

FAQ

Uitgeverij Podium company demonstrates a stronger AI Cybersecurity Score compared to Verbum company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Verbum company has disclosed a higher number of cyber incidents compared to Uitgeverij Podium company.

In the current year, Verbum company and Uitgeverij Podium company have not reported any cyber incidents.

Neither Verbum company nor Uitgeverij Podium company has reported experiencing a ransomware attack publicly.

Neither Verbum company nor Uitgeverij Podium company has reported experiencing a data breach publicly.

Neither Verbum company nor Uitgeverij Podium company has reported experiencing targeted cyberattacks publicly.

Neither Uitgeverij Podium company nor Verbum company has reported experiencing or disclosing vulnerabilities publicly.

Neither Uitgeverij Podium nor Verbum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Uitgeverij Podium company nor Verbum company has publicly disclosed detailed information about the number of their subsidiaries.

Verbum company employs more people globally than Uitgeverij Podium company, reflecting its scale as a Book and Periodical Publishing.

Neither Uitgeverij Podium nor Verbum holds SOC 2 Type 1 certification.

Neither Uitgeverij Podium nor Verbum holds SOC 2 Type 2 certification.

Neither Uitgeverij Podium nor Verbum holds ISO 27001 certification.

Neither Uitgeverij Podium nor Verbum holds PCI DSS certification.

Neither Uitgeverij Podium nor Verbum holds HIPAA certification.

Neither Uitgeverij Podium nor Verbum 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