Comparison Overview

I.O. Metro

VS

Mastercraft Furniture, Inc.

I.O. Metro

316B Commercial Avenue, Lowell, AR, 72745-8868, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.iometro.com

We're a specialty lifestyle home furnishing retailer selling modern furniture, art and accessories in retail stores in several states in the U.S. We offer a custom upholstery line, real wood goods, colorful accessories, large-scale art and more. Our design consultants are designers first, salespeople second. We offer free design service that includes space planning, color consultations, furniture and accessory selection and installation.

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

Mastercraft Furniture, Inc.

None
Last Update: 2025-11-27
Between 750 and 799
http://www.mcfurn.com

Mastercraft Furniture is an American manufacturing company located in the Great Pacific Northwest. Our upholstered furniture is built upon the expertise of three generations of world class furniture builders with over 100 years of combined experience. We build furniture that compliments lives. Each and every piece is crafted with excellence in mind, using only the finest materials available. We want you to love our furniture--and to love it for a lifetime. Made for living. Built to last.

NAICS: 337
NAICS Definition:
Employees: 12
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/i-o--metro.jpeg
I.O. Metro
—
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/mastercraft-furniture-inc-.jpeg
Mastercraft Furniture, Inc.
—
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
I.O. Metro
100%
Compliance Rate
0/4 Standards Verified
Mastercraft Furniture, Inc.
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 I.O. Metro in 2025.

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

No incidents recorded for Mastercraft Furniture, Inc. in 2025.

Incident History — I.O. Metro (X = Date, Y = Severity)

I.O. Metro cyber incidents detection timeline including parent company and subsidiaries

Incident History — Mastercraft Furniture, Inc. (X = Date, Y = Severity)

Mastercraft Furniture, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/i-o--metro.jpeg
I.O. Metro
Incidents

No Incident

https://images.rankiteo.com/companyimages/mastercraft-furniture-inc-.jpeg
Mastercraft Furniture, Inc.
Incidents

No Incident

FAQ

Mastercraft Furniture, Inc. company demonstrates a stronger AI Cybersecurity Score compared to I.O. Metro company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Mastercraft Furniture, Inc. company has disclosed a higher number of cyber incidents compared to I.O. Metro company.

In the current year, Mastercraft Furniture, Inc. company and I.O. Metro company have not reported any cyber incidents.

Neither Mastercraft Furniture, Inc. company nor I.O. Metro company has reported experiencing a ransomware attack publicly.

Neither Mastercraft Furniture, Inc. company nor I.O. Metro company has reported experiencing a data breach publicly.

Neither Mastercraft Furniture, Inc. company nor I.O. Metro company has reported experiencing targeted cyberattacks publicly.

Neither I.O. Metro company nor Mastercraft Furniture, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither I.O. Metro nor Mastercraft Furniture, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither I.O. Metro company nor Mastercraft Furniture, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

I.O. Metro company employs more people globally than Mastercraft Furniture, Inc. company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither I.O. Metro nor Mastercraft Furniture, Inc. holds SOC 2 Type 1 certification.

Neither I.O. Metro nor Mastercraft Furniture, Inc. holds SOC 2 Type 2 certification.

Neither I.O. Metro nor Mastercraft Furniture, Inc. holds ISO 27001 certification.

Neither I.O. Metro nor Mastercraft Furniture, Inc. holds PCI DSS certification.

Neither I.O. Metro nor Mastercraft Furniture, Inc. holds HIPAA certification.

Neither I.O. Metro nor Mastercraft Furniture, Inc. 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