Comparison Overview

Coobeh

VS

LUXY

Coobeh

13/8 Rawlinson St, O'connor, Western Australia, 6163, AU
Last Update: 2025-11-27
View Profile
Between 750 and 799
http://www.coobeh.com.au

Coobeh is a family-owned and operated business located in Perth, Western Australia, specializing in custom TV cabinets and entertainment units. We take pride in designing, fabricating, and installing unique, one-of-a-kind entertainment units tailored to your specific house style. Our meticulous approach considers every aspect of the process, ensuring that your vision seamlessly comes to life. Whether you seek a stylish TV cabinet or an elaborate entertainment center, we are dedicated to delivering quality, custom solutions that meet your needs and reflect your personal style.

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

LUXY

Strada Statale Almisano 6, Lonigo, 36045, IT
Last Update: 2025-11-22
Between 750 and 799
http://www.luxy.com

Luxy was established in 1976 as a small producer of chairs in outsourcing, in one of the most important productive areas of Europe, Italy's northeast. Luxy developed into a highly specialised company in the production of ergonomic and design chairs and sofas. Collaboration with designers like Massimiliano and Doriana Fuksas, Stefano Getzel and Luca Bressan, as well as Gianantonio Perin and Jean Luois Iratzoki, along with the company’s innate vocation for research, experimentation and innovation, accompanied by vast technological know-how and experience, led the company to patent products that were characterised by design and ergonomics that are the symbol of “Made in Italy” products, which are exported to over forty countries, through a network of professionals who are attentive to our customers’ needs. In 2011 the Opera fund became a shareholder of Luxy, conferring the company with additional thrust towards development in markets, with increasingly greater attention to the environment and to conformity with norms for safety. The company is well rooted in the world market, but is in continuous movement to satisfy the demands of its clientele... this is Luxy

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 88
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/coobeh.jpeg
Coobeh
—
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/luxy.jpeg
LUXY
—
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
Coobeh
100%
Compliance Rate
0/4 Standards Verified
LUXY
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 Coobeh in 2025.

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

No incidents recorded for LUXY in 2025.

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

Coobeh cyber incidents detection timeline including parent company and subsidiaries

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

LUXY cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/coobeh.jpeg
Coobeh
Incidents

No Incident

https://images.rankiteo.com/companyimages/luxy.jpeg
LUXY
Incidents

No Incident

FAQ

Coobeh company demonstrates a stronger AI Cybersecurity Score compared to LUXY company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, LUXY company has disclosed a higher number of cyber incidents compared to Coobeh company.

In the current year, LUXY company and Coobeh company have not reported any cyber incidents.

Neither LUXY company nor Coobeh company has reported experiencing a ransomware attack publicly.

Neither LUXY company nor Coobeh company has reported experiencing a data breach publicly.

Neither LUXY company nor Coobeh company has reported experiencing targeted cyberattacks publicly.

Neither Coobeh company nor LUXY company has reported experiencing or disclosing vulnerabilities publicly.

Neither Coobeh nor LUXY holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Coobeh company nor LUXY company has publicly disclosed detailed information about the number of their subsidiaries.

LUXY company employs more people globally than Coobeh company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither Coobeh nor LUXY holds SOC 2 Type 1 certification.

Neither Coobeh nor LUXY holds SOC 2 Type 2 certification.

Neither Coobeh nor LUXY holds ISO 27001 certification.

Neither Coobeh nor LUXY holds PCI DSS certification.

Neither Coobeh nor LUXY holds HIPAA certification.

Neither Coobeh nor LUXY 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