Comparison Overview

Wells County Public Library

VS

Otis Library

Wells County Public Library

200 W. Washington Street, Bluffton, IN, 46714, US
Last Update: 2025-11-29
View Profile
Between 750 and 799
http://www.wellscolibrary.org

Wells County Public Library provides the communities it serves with access, knowledge and growth supporting research, popular interests and lifelong learning. The library is a county library servicing our 27,000+ residents through two facilities in Bluffton and Ossian. Our 130,000+ collections is available in a variety of formats, including print, audio, video, music, electronic, and digital online resources. The library offers a wide variety of programming for all ages and also provides meeting rooms for public use.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 21
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Otis Library

261 Main St, Norwich, CT, 06360, US
Last Update: 2025-11-27
Between 750 and 799
http://www.otislibrarynorwich.org

We are the public library serving Norwich, Connecticut. We are a full service library. Our mission: "Otis Library provides free and open access to information, ideas, and services that anticipate our community’s personal, educational, and professional needs. The library enriches our region by maintaining a safe and welcoming environment and by offering resources that promote lifelong learning."

NAICS: 519
NAICS Definition:
Employees: 22
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/wells-county-public-library.jpeg
Wells County Public Library
—
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/otis-library.jpeg
Otis Library
—
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
Wells County Public Library
100%
Compliance Rate
0/4 Standards Verified
Otis Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Wells County Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Otis Library in 2025.

Incident History — Wells County Public Library (X = Date, Y = Severity)

Wells County Public Library cyber incidents detection timeline including parent company and subsidiaries

Incident History — Otis Library (X = Date, Y = Severity)

Otis Library cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/wells-county-public-library.jpeg
Wells County Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/otis-library.jpeg
Otis Library
Incidents

No Incident

FAQ

Otis Library company demonstrates a stronger AI Cybersecurity Score compared to Wells County Public Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Otis Library company has disclosed a higher number of cyber incidents compared to Wells County Public Library company.

In the current year, Otis Library company and Wells County Public Library company have not reported any cyber incidents.

Neither Otis Library company nor Wells County Public Library company has reported experiencing a ransomware attack publicly.

Neither Otis Library company nor Wells County Public Library company has reported experiencing a data breach publicly.

Neither Otis Library company nor Wells County Public Library company has reported experiencing targeted cyberattacks publicly.

Neither Wells County Public Library company nor Otis Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Wells County Public Library nor Otis Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Wells County Public Library company nor Otis Library company has publicly disclosed detailed information about the number of their subsidiaries.

Otis Library company employs more people globally than Wells County Public Library company, reflecting its scale as a Libraries.

Neither Wells County Public Library nor Otis Library holds SOC 2 Type 1 certification.

Neither Wells County Public Library nor Otis Library holds SOC 2 Type 2 certification.

Neither Wells County Public Library nor Otis Library holds ISO 27001 certification.

Neither Wells County Public Library nor Otis Library holds PCI DSS certification.

Neither Wells County Public Library nor Otis Library holds HIPAA certification.

Neither Wells County Public Library nor Otis Library 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