Comparison Overview

Castle Furniture

VS

4ROOM

Castle Furniture

6965 S. Priest Dr. Suite 1, Tempe, 85283, US
Last Update: 2025-11-22
View Profile
Between 750 and 799
http://www.castlerents.com

Castle Furniture is a family owned and operated furniture company located in Tempe, Arizona. Established in 1993, Castle provides a variety of furniture rental packages, including custom home staging options. Castle also offers housewares rentals, which are processed in house in order to minimize rental costs for customers.

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

4ROOM

76903, EE
Last Update: 2025-11-21
Between 800 and 849
http://www.4room.ee

YOUR TAYLOR IN THE WORLD OF LIGHTS The products of 4ROOM are born at our 4ROOM factory in Estonia from the idea to the ready-made product. We always have a wide selection of solutions, which enable to fulfil the wishes of even the most demanding clients quickly and with high quality! Our history and experience reach back to 1959; since 2003, we are operating under the trademark 4ROOM, which reflects our activities and face best. FOR room or 4 different room-s :) IDEA and DESIGN We take inspiration from life and nature, the product is finished in teamwork with the help of the factory and designers. We never stop before the product is “completely designed”; this is the goal that we follow. It is our desire to be and remain unique and to offer (our) clients bright and timeless lights through our peculiarity. PRODUCTION We create the products to last – just like our grandparents used to. Thus, we use carefully selected natural materials cost-efficiently, but without saving at the expense of quality. All materials and components are certified and manufactured in the EU! EMOTION We only make products that warm our hearts and are easy on our eyes. We sincerely wish to convey the passion put into our products through the products to the client!

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 29
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/defaultcompany.jpeg
Castle Furniture
—
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/4room.jpeg
4ROOM
—
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
Castle Furniture
100%
Compliance Rate
0/4 Standards Verified
4ROOM
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 Castle Furniture in 2025.

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

No incidents recorded for 4ROOM in 2025.

Incident History — Castle Furniture (X = Date, Y = Severity)

Castle Furniture cyber incidents detection timeline including parent company and subsidiaries

Incident History — 4ROOM (X = Date, Y = Severity)

4ROOM cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Castle Furniture
Incidents

No Incident

https://images.rankiteo.com/companyimages/4room.jpeg
4ROOM
Incidents

No Incident

FAQ

4ROOM company demonstrates a stronger AI Cybersecurity Score compared to Castle Furniture company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, 4ROOM company has disclosed a higher number of cyber incidents compared to Castle Furniture company.

In the current year, 4ROOM company and Castle Furniture company have not reported any cyber incidents.

Neither 4ROOM company nor Castle Furniture company has reported experiencing a ransomware attack publicly.

Neither 4ROOM company nor Castle Furniture company has reported experiencing a data breach publicly.

Neither 4ROOM company nor Castle Furniture company has reported experiencing targeted cyberattacks publicly.

Neither Castle Furniture company nor 4ROOM company has reported experiencing or disclosing vulnerabilities publicly.

Neither Castle Furniture nor 4ROOM holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Castle Furniture company nor 4ROOM company has publicly disclosed detailed information about the number of their subsidiaries.

Castle Furniture company employs more people globally than 4ROOM company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither Castle Furniture nor 4ROOM holds SOC 2 Type 1 certification.

Neither Castle Furniture nor 4ROOM holds SOC 2 Type 2 certification.

Neither Castle Furniture nor 4ROOM holds ISO 27001 certification.

Neither Castle Furniture nor 4ROOM holds PCI DSS certification.

Neither Castle Furniture nor 4ROOM holds HIPAA certification.

Neither Castle Furniture nor 4ROOM 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