Comparison Overview

Burlington Furniture Company

VS

Saloom Furniture Company

Burlington Furniture Company

747 Pine Street, Burlington, VT, 05401, US
Last Update: 2025-11-21

We are Vermont's destination for classic contemporary furniture. Our brand new 28,000 square feet showroom acts as a Design Center where our design associates can provide interior design services to help transform your house into a home. As members of the Contemporary Design Group we shop the world to bring unique products to our store and to your home. Burlington Furniture Company was founded in 1984 and is locally owned and operated. We are guided by a triple bottom line that includes our commitment to our local community and to the environment that sustains us.

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

Saloom Furniture Company

256 Murdock Avenue, Winchendon, MA, 01475, US
Last Update: 2025-11-26
Between 750 and 799

Saloom Furniture Company is a premier supplier of dining room furniture sets of all styles. We make contemporary, transitional and country dining tables, dining chairs and case pieces in maple and cherry in the heart of New England. Our furniture can be found at locations throughout the United States and Canada. To find a dealer near you, check out our store locator at http://www.saloom.com.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 16
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/burlington-furniture-company.jpeg
Burlington Furniture Company
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/saloom-furniture-company.jpeg
Saloom Furniture Company
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
Burlington Furniture Company
100%
Compliance Rate
0/4 Standards Verified
Saloom Furniture Company
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 Burlington Furniture Company in 2025.

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

No incidents recorded for Saloom Furniture Company in 2025.

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

Burlington Furniture Company cyber incidents detection timeline including parent company and subsidiaries

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

Saloom Furniture Company cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/burlington-furniture-company.jpeg
Burlington Furniture Company
Incidents

No Incident

https://images.rankiteo.com/companyimages/saloom-furniture-company.jpeg
Saloom Furniture Company
Incidents

No Incident

FAQ

Saloom Furniture Company company demonstrates a stronger AI Cybersecurity Score compared to Burlington Furniture Company company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Saloom Furniture Company company has disclosed a higher number of cyber incidents compared to Burlington Furniture Company company.

In the current year, Saloom Furniture Company company and Burlington Furniture Company company have not reported any cyber incidents.

Neither Saloom Furniture Company company nor Burlington Furniture Company company has reported experiencing a ransomware attack publicly.

Neither Saloom Furniture Company company nor Burlington Furniture Company company has reported experiencing a data breach publicly.

Neither Saloom Furniture Company company nor Burlington Furniture Company company has reported experiencing targeted cyberattacks publicly.

Neither Burlington Furniture Company company nor Saloom Furniture Company company has reported experiencing or disclosing vulnerabilities publicly.

Neither Burlington Furniture Company nor Saloom Furniture Company holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Burlington Furniture Company company nor Saloom Furniture Company company has publicly disclosed detailed information about the number of their subsidiaries.

Saloom Furniture Company company employs more people globally than Burlington Furniture Company company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither Burlington Furniture Company nor Saloom Furniture Company holds SOC 2 Type 1 certification.

Neither Burlington Furniture Company nor Saloom Furniture Company holds SOC 2 Type 2 certification.

Neither Burlington Furniture Company nor Saloom Furniture Company holds ISO 27001 certification.

Neither Burlington Furniture Company nor Saloom Furniture Company holds PCI DSS certification.

Neither Burlington Furniture Company nor Saloom Furniture Company holds HIPAA certification.

Neither Burlington Furniture Company nor Saloom Furniture Company 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.

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
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).

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
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

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
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.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.