Comparison Overview

Peabody Office

VS

Yaasa Studios Inc.

Peabody Office

234 Congress Street, Boston, 02110, US
Last Update: 2025-11-21
View Profile
Between 750 and 799
http://www.peabodyoffice.com

As one of New England's oldest furniture dealers, Peabody has a long line of success that extends over 120 years. Today, Peabody remains a family-owned and operated organization and continues to provide New England's business community with progressive office solutions and services. We are proud of our longtime affiliation with our manufacturing partners, and we are always looking for companies and new partners who are committed to good design. We work in tandem with Architects, Designers, Landlords, Brokers, Project Management Firms, and Corporate End Users to facilitate all aspects of furniture procurement and implement responsive workspace solutions.

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

Yaasa Studios Inc.

3016 De La Vina St, Santa Barbara, California, 93105, US
Last Update: 2025-11-27
Between 750 and 799
https://yaasa.com

Yaasa is the world’s leading adjustable furniture company. We specialize in making traditionally static furniture move. Adjustability is in everything we design and manufacture. In our core products, the Yaasa Adjustable Bed, Desk and Chair, the adjustment factor is evident, but all our products have adjustability built-in, working with your every need to ensure you live a life perfectly well-adjusted.

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/peabody-office.jpeg
Peabody Office
—
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/yaasastudios.jpeg
Yaasa Studios 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
Peabody Office
100%
Compliance Rate
0/4 Standards Verified
Yaasa Studios 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 Peabody Office in 2025.

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

No incidents recorded for Yaasa Studios Inc. in 2025.

Incident History — Peabody Office (X = Date, Y = Severity)

Peabody Office cyber incidents detection timeline including parent company and subsidiaries

Incident History — Yaasa Studios Inc. (X = Date, Y = Severity)

Yaasa Studios Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/peabody-office.jpeg
Peabody Office
Incidents

No Incident

https://images.rankiteo.com/companyimages/yaasastudios.jpeg
Yaasa Studios Inc.
Incidents

No Incident

FAQ

Peabody Office company demonstrates a stronger AI Cybersecurity Score compared to Yaasa Studios Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Yaasa Studios Inc. company has disclosed a higher number of cyber incidents compared to Peabody Office company.

In the current year, Yaasa Studios Inc. company and Peabody Office company have not reported any cyber incidents.

Neither Yaasa Studios Inc. company nor Peabody Office company has reported experiencing a ransomware attack publicly.

Neither Yaasa Studios Inc. company nor Peabody Office company has reported experiencing a data breach publicly.

Neither Yaasa Studios Inc. company nor Peabody Office company has reported experiencing targeted cyberattacks publicly.

Neither Peabody Office company nor Yaasa Studios Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Peabody Office nor Yaasa Studios Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Peabody Office company nor Yaasa Studios Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Peabody Office company employs more people globally than Yaasa Studios Inc. company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither Peabody Office nor Yaasa Studios Inc. holds SOC 2 Type 1 certification.

Neither Peabody Office nor Yaasa Studios Inc. holds SOC 2 Type 2 certification.

Neither Peabody Office nor Yaasa Studios Inc. holds ISO 27001 certification.

Neither Peabody Office nor Yaasa Studios Inc. holds PCI DSS certification.

Neither Peabody Office nor Yaasa Studios Inc. holds HIPAA certification.

Neither Peabody Office nor Yaasa Studios 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