Comparison Overview

Hitch Mylius Ltd.

VS

Wycombe21

Hitch Mylius Ltd.

12 Greenhill Rents, LONDON, EC1M 6BN, GB
Last Update: 2025-11-22
View Profile
Between 750 and 799
http://www.hitchmylius.co.uk

We have been making beautiful and contemporary upholstered furniture in north London for over 50 years. Our product collection combines in-house designs with creative collaborations from a diverse and eclectic mix of designers and architects. We supply our furniture to clients around the world, populating working and living environments in all sectors. Our comprehensive collection has organically developed to acknowledge the changing needs of these spaces and possesses longevity in design and manufacturing terms, that our customers can consistently rely on.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 11
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Wycombe21

Hillbottom Road, High Wycombe, Buckinghamshire, HP12 4HJ, GB
Last Update: 2025-11-26
Between 750 and 799
https://www.wycombe21.co.uk

WYCOMBE 21. At Wycombe 21 our aim is to continue the heritage of high quality furniture design and manufacture from the area, with a 21st century flavour. We have put together a flexible and practical range of standard products which are complemented by our ability to provide bespoke design services on any project. We really are experts when it comes to working on those complicated, specialised bespoke projects. We are constantly consulting with Product Designers, Interior Designers and Furniture Dealers to make sure we are developing products relevant to today’s market.

NAICS: 337
NAICS Definition:
Employees: 1
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/hitch-mylius-ltd-.jpeg
Hitch Mylius 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/wycombe21.jpeg
Wycombe21
—
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
Hitch Mylius Ltd.
100%
Compliance Rate
0/4 Standards Verified
Wycombe21
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Furniture and Home Furnishings Manufacturing Industry Average (This Year)

No incidents recorded for Hitch Mylius Ltd. in 2025.

Incidents vs Furniture and Home Furnishings Manufacturing Industry Average (This Year)

No incidents recorded for Wycombe21 in 2025.

Incident History — Hitch Mylius Ltd. (X = Date, Y = Severity)

Hitch Mylius Ltd. cyber incidents detection timeline including parent company and subsidiaries

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

Wycombe21 cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hitch-mylius-ltd-.jpeg
Hitch Mylius Ltd.
Incidents

No Incident

https://images.rankiteo.com/companyimages/wycombe21.jpeg
Wycombe21
Incidents

No Incident

FAQ

Both Hitch Mylius Ltd. company and Wycombe21 company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Wycombe21 company has disclosed a higher number of cyber incidents compared to Hitch Mylius Ltd. company.

In the current year, Wycombe21 company and Hitch Mylius Ltd. company have not reported any cyber incidents.

Neither Wycombe21 company nor Hitch Mylius Ltd. company has reported experiencing a ransomware attack publicly.

Neither Wycombe21 company nor Hitch Mylius Ltd. company has reported experiencing a data breach publicly.

Neither Wycombe21 company nor Hitch Mylius Ltd. company has reported experiencing targeted cyberattacks publicly.

Neither Hitch Mylius Ltd. company nor Wycombe21 company has reported experiencing or disclosing vulnerabilities publicly.

Neither Hitch Mylius Ltd. nor Wycombe21 holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Hitch Mylius Ltd. company nor Wycombe21 company has publicly disclosed detailed information about the number of their subsidiaries.

Hitch Mylius Ltd. company employs more people globally than Wycombe21 company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither Hitch Mylius Ltd. nor Wycombe21 holds SOC 2 Type 1 certification.

Neither Hitch Mylius Ltd. nor Wycombe21 holds SOC 2 Type 2 certification.

Neither Hitch Mylius Ltd. nor Wycombe21 holds ISO 27001 certification.

Neither Hitch Mylius Ltd. nor Wycombe21 holds PCI DSS certification.

Neither Hitch Mylius Ltd. nor Wycombe21 holds HIPAA certification.

Neither Hitch Mylius Ltd. nor Wycombe21 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