Comparison Overview

Codice Edizioni

VS

Circulo de Lectores

Codice Edizioni

via San Francesco da Paola, 37, Torino, 10123, IT
Last Update: 2025-11-21
Between 750 and 799

Codice Edizioni si costituisce a Torino nel settembre 2003, come naturale prosecuzione del progetto elaborato attraverso la costituzione della società Codice. Idee per la Cultura, con l’intento di rinnovare una tradizione editoriale orientata alla riflessione saggistica, al dibattito sulla contemporaneità e alla divulgazione scientifica in un momento di particolare interesse da parte dei lettori verso nuove forme di consumo editoriale.

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

Circulo de Lectores

Travessera de Gràcia 47-49, Barcelona, 08021, ES
Last Update: 2025-11-21
Between 750 and 799

Círculo de Lectores es una empresa española con sede en Barcelona, creada por Reinhard Mohn, presidente del grupo alemán Bertelsmann, y José Esteve Quintana, fundador de la editorial Vergara en 1962 para distribuir, en un modelo club, libros y productos culturales de calidad en todo el territorio nacional, con el objetivo de ser un punto de encuentro entre autores y lectores y facilitar la distribución de la cultura. Durante estas casi cinco décadas de historia, Círculo se ha convertido en empresa de referencia en el mundo del libro y la lectura en España, ya que ofrece a sus socios la mejor selección literaria del panorama nacional e internacional, en una edición propia y de gran calidad. Círculo forma parte del grupo Bertelsmann, con presencia en 63 países del mundo, y del grupo Planeta, el primer grupo de comunicación español con presencia en Europa y América Latina, con más de 70 editoriales. Éste último se incorporaba al accionariado en abril de 2010.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 447
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/codice-edizioni.jpeg
Codice Edizioni
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/circulo-de-lectores.jpeg
Circulo de Lectores
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
Codice Edizioni
100%
Compliance Rate
0/4 Standards Verified
Circulo de Lectores
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 Codice Edizioni in 2025.

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

No incidents recorded for Circulo de Lectores in 2025.

Incident History — Codice Edizioni (X = Date, Y = Severity)

Codice Edizioni cyber incidents detection timeline including parent company and subsidiaries

Incident History — Circulo de Lectores (X = Date, Y = Severity)

Circulo de Lectores cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/codice-edizioni.jpeg
Codice Edizioni
Incidents

No Incident

https://images.rankiteo.com/companyimages/circulo-de-lectores.jpeg
Circulo de Lectores
Incidents

No Incident

FAQ

Circulo de Lectores company demonstrates a stronger AI Cybersecurity Score compared to Codice Edizioni company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Circulo de Lectores company has disclosed a higher number of cyber incidents compared to Codice Edizioni company.

In the current year, Circulo de Lectores company and Codice Edizioni company have not reported any cyber incidents.

Neither Circulo de Lectores company nor Codice Edizioni company has reported experiencing a ransomware attack publicly.

Neither Circulo de Lectores company nor Codice Edizioni company has reported experiencing a data breach publicly.

Neither Circulo de Lectores company nor Codice Edizioni company has reported experiencing targeted cyberattacks publicly.

Neither Codice Edizioni company nor Circulo de Lectores company has reported experiencing or disclosing vulnerabilities publicly.

Neither Codice Edizioni nor Circulo de Lectores holds any compliance certifications.

Neither company holds any compliance certifications.

Codice Edizioni company has more subsidiaries worldwide compared to Circulo de Lectores company.

Circulo de Lectores company employs more people globally than Codice Edizioni company, reflecting its scale as a Book and Periodical Publishing.

Neither Codice Edizioni nor Circulo de Lectores holds SOC 2 Type 1 certification.

Neither Codice Edizioni nor Circulo de Lectores holds SOC 2 Type 2 certification.

Neither Codice Edizioni nor Circulo de Lectores holds ISO 27001 certification.

Neither Codice Edizioni nor Circulo de Lectores holds PCI DSS certification.

Neither Codice Edizioni nor Circulo de Lectores holds HIPAA certification.

Neither Codice Edizioni nor Circulo de Lectores 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.