Comparison Overview

Demos Medical Publishing

VS

Hampton Publishing

Demos Medical Publishing

11 W. 42nd Street, New York, NY, 10036, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.demosmedical.com

For more than 25 years, Demos Medical Publishing has served the information needs of medical professionals. We publish high-quality books and digital products for physicians and other healthcare providers, and have established an international reputation for excellence in our core areas of neurology, physical medicine and rehabilitation, pathology, and oncology. Demos Medical Publishing was acquired by Mannheim Holdings, LLC, a subsidiary of the Mannheim Trust, New York, in 2004 and is today a subsidiary of Springer Publishing Company. For more information, see http://www.demosmedical.com.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 8
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Hampton Publishing

8264 Cardnia Ct., Liberty Twp, OH, 45044, US
Last Update: 2025-11-27
Between 750 and 799
http://www.hamptonpublish.com

Hampton Publishing, Inc. is a top quality Magazine, Directory, Guide, Book, and Map publisher. Since 1976, we have dedicated ourselves to helping your Chamber or organization “look your Best” and project a positive image for your community . Over the past three decades our experienced staff has produced thousands of successful projects; many of which are funded by member advertising. We offer a plethora of publishing services, including concept, research, writing, editing, sales and marketing, photo shoots, design, production, manufacturing and cartography. An interactive digital format is available for every publication we produce. Hampton Publishing, values the relationship we have with our customers and treats our clients as partners. We look forward to working together to improve and enhance your publication and marketing tools.

NAICS: 511
NAICS Definition:
Employees: 2
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/demos-medical-publishing.jpeg
Demos Medical Publishing
—
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/hampton-publishing.jpeg
Hampton Publishing
—
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
Demos Medical Publishing
100%
Compliance Rate
0/4 Standards Verified
Hampton Publishing
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Demos Medical Publishing in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Hampton Publishing in 2025.

Incident History — Demos Medical Publishing (X = Date, Y = Severity)

Demos Medical Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hampton Publishing (X = Date, Y = Severity)

Hampton Publishing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/demos-medical-publishing.jpeg
Demos Medical Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/hampton-publishing.jpeg
Hampton Publishing
Incidents

No Incident

FAQ

Hampton Publishing company demonstrates a stronger AI Cybersecurity Score compared to Demos Medical Publishing company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Hampton Publishing company has disclosed a higher number of cyber incidents compared to Demos Medical Publishing company.

In the current year, Hampton Publishing company and Demos Medical Publishing company have not reported any cyber incidents.

Neither Hampton Publishing company nor Demos Medical Publishing company has reported experiencing a ransomware attack publicly.

Neither Hampton Publishing company nor Demos Medical Publishing company has reported experiencing a data breach publicly.

Neither Hampton Publishing company nor Demos Medical Publishing company has reported experiencing targeted cyberattacks publicly.

Neither Demos Medical Publishing company nor Hampton Publishing company has reported experiencing or disclosing vulnerabilities publicly.

Neither Demos Medical Publishing nor Hampton Publishing holds any compliance certifications.

Neither company holds any compliance certifications.

Demos Medical Publishing company has more subsidiaries worldwide compared to Hampton Publishing company.

Demos Medical Publishing company employs more people globally than Hampton Publishing company, reflecting its scale as a Book and Periodical Publishing.

Neither Demos Medical Publishing nor Hampton Publishing holds SOC 2 Type 1 certification.

Neither Demos Medical Publishing nor Hampton Publishing holds SOC 2 Type 2 certification.

Neither Demos Medical Publishing nor Hampton Publishing holds ISO 27001 certification.

Neither Demos Medical Publishing nor Hampton Publishing holds PCI DSS certification.

Neither Demos Medical Publishing nor Hampton Publishing holds HIPAA certification.

Neither Demos Medical Publishing nor Hampton Publishing 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