Comparison Overview

Doylestown Historical Society

VS

Lincoln Park Zoo

Doylestown Historical Society

56 S Main St, Doylestown, Pennsylvania, 18901, US
Last Update: 2026-01-23

"Preserving and celebrating the creative and historic significance of Doylestown and its neighboring communities"​. Collecting and preserving artifacts of our past is a major activity of the Society. But we also collect stories. The narratives are the human connection to our past and it is these stories that help bring history alive. Without the stories, all those photos, documents, and objects are just interesting things to look at. We also celebrate our past with events that commemorate Doylestown's people, places and events, so that they may long be remembered.

NAICS: 712
NAICS Definition:
Employees: 5
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Lincoln Park Zoo

2001 North Clark Street, Chicago, IL, 60614, US
Last Update: 2026-01-22
Between 750 and 799

Lincoln Park Zoo inspires communities to create environments where wildlife will thrive in our urbanizing world. The zoo is a leader in local and global conservation, animal care and welfare, learning, and science. A historic Chicago landmark founded in 1868, the not-for-profit Lincoln Park Zoo, is a privately-managed, member-supported organization and is free and open 365 days a year.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 412
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/doylestownhistorical.jpeg
Doylestown Historical Society
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/lincoln-park-zoo.jpeg
Lincoln Park Zoo
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
Doylestown Historical Society
100%
Compliance Rate
0/4 Standards Verified
Lincoln Park Zoo
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Museums, Historical Sites, and Zoos Industry Average (This Year)

No incidents recorded for Doylestown Historical Society in 2026.

Incidents vs Museums, Historical Sites, and Zoos Industry Average (This Year)

No incidents recorded for Lincoln Park Zoo in 2026.

Incident History — Doylestown Historical Society (X = Date, Y = Severity)

Doylestown Historical Society cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lincoln Park Zoo (X = Date, Y = Severity)

Lincoln Park Zoo cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/doylestownhistorical.jpeg
Doylestown Historical Society
Incidents

No Incident

https://images.rankiteo.com/companyimages/lincoln-park-zoo.jpeg
Lincoln Park Zoo
Incidents

No Incident

FAQ

Lincoln Park Zoo company demonstrates a stronger AI Cybersecurity Score compared to Doylestown Historical Society company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Lincoln Park Zoo company has disclosed a higher number of cyber incidents compared to Doylestown Historical Society company.

In the current year, Lincoln Park Zoo company and Doylestown Historical Society company have not reported any cyber incidents.

Neither Lincoln Park Zoo company nor Doylestown Historical Society company has reported experiencing a ransomware attack publicly.

Neither Lincoln Park Zoo company nor Doylestown Historical Society company has reported experiencing a data breach publicly.

Neither Lincoln Park Zoo company nor Doylestown Historical Society company has reported experiencing targeted cyberattacks publicly.

Neither Doylestown Historical Society company nor Lincoln Park Zoo company has reported experiencing or disclosing vulnerabilities publicly.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Doylestown Historical Society company nor Lincoln Park Zoo company has publicly disclosed detailed information about the number of their subsidiaries.

Lincoln Park Zoo company employs more people globally than Doylestown Historical Society company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds SOC 2 Type 1 certification.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds SOC 2 Type 2 certification.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds ISO 27001 certification.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds PCI DSS certification.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds HIPAA certification.

Neither Doylestown Historical Society nor Lincoln Park Zoo holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Description

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.