Comparison Overview

J&J Editorial: A Wiley Brand

VS

DotLib

J&J Editorial: A Wiley Brand

201 Shannon Oaks Circle, Cary, NC, 27511, US
Last Update: 2025-11-21
Between 750 and 799

J&J Editorial is an publishing services company dedicated to providing efficient and professional support to editorial offices, publishers, and societies. J&J’s employees work in partnership with clients to understand their unique needs and offer a range of editorial, production, copyediting, and submission platform support services to meet those needs at a consistent level of excellence. J&J Editorial is a Wiley brand. Wiley champions those who see knowledge as a force for good. A trusted leader in research and learning, our pioneering solutions and services are paving the way for knowledge seekers as they work to solve the world’s most important challenges. Around the globe, we break down barriers for innovators, empowering them to publish and advance discoveries in their fields, evolve their workforces, and shape minds through teaching and learning. Together, we are unlocking the creation and curation of knowledge for all, transforming today’s biggest obstacles into tomorrow’s brightest opportunities. Visit Wiley at Wiley.com. Follow us on Twitter! @jjeditorial

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

DotLib

Avenida Ayrton Senna, 2600, Rio de Janeiro, RJ, 22775-003, BR
Last Update: 2025-11-26
Between 750 and 799

A Dot.Lib é uma empresa brasileira dedicada à disseminação da informação científica através do fornecimento de acesso online a livros digitais, periódicos eletrônicos e bases de dados nas principais áreas do conhecimento: Ciências Agrárias, Ciências Biológicas, Ciências da Saúde, Ciências Exatas e da Terra, Ciências Humanas, Ciências Sociais Aplicadas, Engenharias e Artes.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 52
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/j&j-editorial.jpeg
J&J Editorial: A Wiley Brand
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/dotlib.jpeg
DotLib
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
J&J Editorial: A Wiley Brand
100%
Compliance Rate
0/4 Standards Verified
DotLib
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 J&J Editorial: A Wiley Brand in 2025.

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

No incidents recorded for DotLib in 2025.

Incident History — J&J Editorial: A Wiley Brand (X = Date, Y = Severity)

J&J Editorial: A Wiley Brand cyber incidents detection timeline including parent company and subsidiaries

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

DotLib cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/j&j-editorial.jpeg
J&J Editorial: A Wiley Brand
Incidents

Date Detected: 9/2025
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/dotlib.jpeg
DotLib
Incidents

No Incident

FAQ

J&J Editorial: A Wiley Brand company demonstrates a stronger AI Cybersecurity Score compared to DotLib company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

J&J Editorial: A Wiley Brand company has historically faced a number of disclosed cyber incidents, whereas DotLib company has not reported any.

In the current year, J&J Editorial: A Wiley Brand company has reported more cyber incidents than DotLib company.

Neither DotLib company nor J&J Editorial: A Wiley Brand company has reported experiencing a ransomware attack publicly.

J&J Editorial: A Wiley Brand company has disclosed at least one data breach, while the other DotLib company has not reported such incidents publicly.

Neither DotLib company nor J&J Editorial: A Wiley Brand company has reported experiencing targeted cyberattacks publicly.

Neither J&J Editorial: A Wiley Brand company nor DotLib company has reported experiencing or disclosing vulnerabilities publicly.

Neither J&J Editorial: A Wiley Brand nor DotLib holds any compliance certifications.

Neither company holds any compliance certifications.

J&J Editorial: A Wiley Brand company has more subsidiaries worldwide compared to DotLib company.

J&J Editorial: A Wiley Brand company employs more people globally than DotLib company, reflecting its scale as a Book and Periodical Publishing.

Neither J&J Editorial: A Wiley Brand nor DotLib holds SOC 2 Type 1 certification.

Neither J&J Editorial: A Wiley Brand nor DotLib holds SOC 2 Type 2 certification.

Neither J&J Editorial: A Wiley Brand nor DotLib holds ISO 27001 certification.

Neither J&J Editorial: A Wiley Brand nor DotLib holds PCI DSS certification.

Neither J&J Editorial: A Wiley Brand nor DotLib holds HIPAA certification.

Neither J&J Editorial: A Wiley Brand nor DotLib 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.