Comparison Overview

Paper Rose Ltd

VS

Leya

Paper Rose Ltd

Centurion Way, Nottingham, England, NG2 1, GB
Last Update: 2025-11-26
View Profile
Between 750 and 799
https://www.paperrose.co.uk

With over 37 years in the greeting card business we have built up a reputation for beautiful, high quality designs at a great price, with the whole buying experience supported by excellent customer service. Offering a dazzling array of over 1500 amazing cards to choose from there is sure to be something for every occasion. Our design team work with some of the most talented artists in the industry to create the best in design and innovation. 2025 sees an emphasis on our eco-friendly status with the launch of Artisan Eco-Handmade featuring Paper Gems. We proudly print on FSC certified board and are continuing to work alongside leading industry bodies with a focus to reduce the industry’s plastic usage.

NAICS: 511
NAICS Definition:
Employees: 19
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Leya

Rua Cidade de Cordova 2, Amadora, 2610-038, PT
Last Update: 2025-11-21
Between 750 and 799
http://www.leya.com

A LeYa nasceu em 2008 como grupo editorial no qual se integram algumas das mais prestigiadas editoras de língua portuguesa. Líder do mercado editorial português, angolano e moçambicano, a LeYa está também presente no Brasil onde atua no setor do ensino a distância / e-learning. A força das marcas que integram a LeYa, os autores com que temos o privilégio de trabalhar e a qualidade do que, em conjunto, criamos fazem da LeYa uma empresa forte e coesa nos seus objetivos gerais e diversificada nos seus programas editoriais, bem como nas suas atividades na área da Educação. Graças à integração de empresas e de profissionais profundamente enraizados nos respetivos mercados, a LeYa conta hoje com um capital humano extraordinário e detentor de um sólido e diversificado know-how nos meios Editorial, Educativo e Tecnológico. Nos mercados onde opera, a LeYa apresenta-se com objetivos concretos de vir a ser protagonista, nomeadamente pelo papel que desempenha no mundo de língua portuguesa.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 581
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/paper-rose-ltd.jpeg
Paper Rose Ltd
—
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/grupo-leya.jpeg
Leya
—
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
Paper Rose Ltd
100%
Compliance Rate
0/4 Standards Verified
Leya
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 Paper Rose Ltd in 2025.

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

No incidents recorded for Leya in 2025.

Incident History — Paper Rose Ltd (X = Date, Y = Severity)

Paper Rose Ltd cyber incidents detection timeline including parent company and subsidiaries

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

Leya cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/paper-rose-ltd.jpeg
Paper Rose Ltd
Incidents

No Incident

https://images.rankiteo.com/companyimages/grupo-leya.jpeg
Leya
Incidents

No Incident

FAQ

Leya company demonstrates a stronger AI Cybersecurity Score compared to Paper Rose Ltd company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Leya company has disclosed a higher number of cyber incidents compared to Paper Rose Ltd company.

In the current year, Leya company and Paper Rose Ltd company have not reported any cyber incidents.

Neither Leya company nor Paper Rose Ltd company has reported experiencing a ransomware attack publicly.

Neither Leya company nor Paper Rose Ltd company has reported experiencing a data breach publicly.

Neither Leya company nor Paper Rose Ltd company has reported experiencing targeted cyberattacks publicly.

Neither Paper Rose Ltd company nor Leya company has reported experiencing or disclosing vulnerabilities publicly.

Neither Paper Rose Ltd nor Leya holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Paper Rose Ltd company nor Leya company has publicly disclosed detailed information about the number of their subsidiaries.

Leya company employs more people globally than Paper Rose Ltd company, reflecting its scale as a Book and Periodical Publishing.

Neither Paper Rose Ltd nor Leya holds SOC 2 Type 1 certification.

Neither Paper Rose Ltd nor Leya holds SOC 2 Type 2 certification.

Neither Paper Rose Ltd nor Leya holds ISO 27001 certification.

Neither Paper Rose Ltd nor Leya holds PCI DSS certification.

Neither Paper Rose Ltd nor Leya holds HIPAA certification.

Neither Paper Rose Ltd nor Leya 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