Comparison Overview

Editorial Ink

VS

Society of Young Publishers

Editorial Ink

Santa Fe,, Distrito Federal, 01210, MX
Last Update: 2025-11-21
Between 750 and 799

[email protected] ESPAÑOL Editorial Ink, primera editorial mexicana 100% digital. Forbes la reconoce como pionera de eBooks en México. Con presencia mundial en Amazon, Apple, B&N, Google Play y Kobo. Ofrece servicios digitales como la única de habla hispana certificada por Apple como casa convertidora, agregadora de contenido y distribuidora. Reinventando el arte de leer. INGLÉS Editorial Ink, first 100% digital Mexican publishing house. Recognized by Forbes as the eBook pioneer in Mexico. With worldwide presence in Amazon, Apple, B&N, Google Play and Kobo. Offers digital services as the only Spanish-speaking conversion house, content aggregator and distributor certified by Apple. Reinventing the art of reading.

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

Society of Young Publishers

We can be reached by snail mail at:, London, undefined, WC1B 5BW, GB
Last Update: 2025-11-26
Between 750 and 799

Established in 1949, the Society of Young Publishers is open to anyone in publishing or a related trade (in any capacity) – or who is hoping to be soon. Run by a team of dedicated volunteers our aim is to help assist, inform and enthuse anyone trying to break into the publishing industry or progress within it. We organise a large number of events, which you can learn more about on our website, and publish a regular magazine called InPrint. Some services, such as job ads, are available only to members.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/editorial-ink.jpeg
Editorial Ink
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/society-of-young-publishers.jpeg
Society of Young Publishers
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
Editorial Ink
100%
Compliance Rate
0/4 Standards Verified
Society of Young Publishers
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 Editorial Ink in 2025.

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

No incidents recorded for Society of Young Publishers in 2025.

Incident History — Editorial Ink (X = Date, Y = Severity)

Editorial Ink cyber incidents detection timeline including parent company and subsidiaries

Incident History — Society of Young Publishers (X = Date, Y = Severity)

Society of Young Publishers cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/editorial-ink.jpeg
Editorial Ink
Incidents

No Incident

https://images.rankiteo.com/companyimages/society-of-young-publishers.jpeg
Society of Young Publishers
Incidents

No Incident

FAQ

Editorial Ink company demonstrates a stronger AI Cybersecurity Score compared to Society of Young Publishers company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Society of Young Publishers company has disclosed a higher number of cyber incidents compared to Editorial Ink company.

In the current year, Society of Young Publishers company and Editorial Ink company have not reported any cyber incidents.

Neither Society of Young Publishers company nor Editorial Ink company has reported experiencing a ransomware attack publicly.

Neither Society of Young Publishers company nor Editorial Ink company has reported experiencing a data breach publicly.

Neither Society of Young Publishers company nor Editorial Ink company has reported experiencing targeted cyberattacks publicly.

Neither Editorial Ink company nor Society of Young Publishers company has reported experiencing or disclosing vulnerabilities publicly.

Neither Editorial Ink nor Society of Young Publishers holds any compliance certifications.

Neither company holds any compliance certifications.

Society of Young Publishers company has more subsidiaries worldwide compared to Editorial Ink company.

Society of Young Publishers company employs more people globally than Editorial Ink company, reflecting its scale as a Book and Periodical Publishing.

Neither Editorial Ink nor Society of Young Publishers holds SOC 2 Type 1 certification.

Neither Editorial Ink nor Society of Young Publishers holds SOC 2 Type 2 certification.

Neither Editorial Ink nor Society of Young Publishers holds ISO 27001 certification.

Neither Editorial Ink nor Society of Young Publishers holds PCI DSS certification.

Neither Editorial Ink nor Society of Young Publishers holds HIPAA certification.

Neither Editorial Ink nor Society of Young Publishers 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.