Comparison Overview

Bookanory Publishing House

VS

Mud Puddle Inc.

Bookanory Publishing House

None
Last Update: 2025-11-21
Between 750 and 799

Bookanory Publishing House centres on providing book services to self-publishing authors, professional authors and publishers. In particular, we provide: 1. High quality book cover graphic designs 2. Interior book formats. We specialise in Microsoft Word format design so that customers will be better placed to make their own post-published edits (assuming they write in Word). Our target market is predominantly (but not exclusively) self-publishing authors – on an online global basis. You may visit the main Bookanory web site at www.bookanory.com for further details and examples of our work. The company is directed by T. J. P. Campbell. His LinkedIn page is: https://www.linkedin.com/in/t-j-p-campbell-13017096

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

Mud Puddle Inc.

36 W. 25th St. Floor 5, New York, New York, 10010, US
Last Update: 2025-11-25
Between 750 and 799

Mud Puddle, Inc. is an independently-owned publishing, packaging and product development company located in New York City. We specialize in creating books, kits, toys and other products that offer exceptional value. Our goal is always to create a tactile experience that is beautiful, informative and engaging. Mud Puddle also does private label publishing in North America and Europe, and we can adapt our products for a variety of different markets, price-points and age groups.

NAICS: 511
NAICS Definition:
Employees: 13
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/bookanory-publishing-house.jpeg
Bookanory Publishing House
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/mud-puddle-inc-.jpeg
Mud Puddle 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
Bookanory Publishing House
100%
Compliance Rate
0/4 Standards Verified
Mud Puddle Inc.
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 Bookanory Publishing House in 2025.

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

No incidents recorded for Mud Puddle Inc. in 2025.

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

Bookanory Publishing House cyber incidents detection timeline including parent company and subsidiaries

Incident History — Mud Puddle Inc. (X = Date, Y = Severity)

Mud Puddle Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bookanory-publishing-house.jpeg
Bookanory Publishing House
Incidents

No Incident

https://images.rankiteo.com/companyimages/mud-puddle-inc-.jpeg
Mud Puddle Inc.
Incidents

No Incident

FAQ

Bookanory Publishing House company demonstrates a stronger AI Cybersecurity Score compared to Mud Puddle Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Mud Puddle Inc. company has disclosed a higher number of cyber incidents compared to Bookanory Publishing House company.

In the current year, Mud Puddle Inc. company and Bookanory Publishing House company have not reported any cyber incidents.

Neither Mud Puddle Inc. company nor Bookanory Publishing House company has reported experiencing a ransomware attack publicly.

Neither Mud Puddle Inc. company nor Bookanory Publishing House company has reported experiencing a data breach publicly.

Neither Mud Puddle Inc. company nor Bookanory Publishing House company has reported experiencing targeted cyberattacks publicly.

Neither Bookanory Publishing House company nor Mud Puddle Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bookanory Publishing House nor Mud Puddle Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Bookanory Publishing House company nor Mud Puddle Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Mud Puddle Inc. company employs more people globally than Bookanory Publishing House company, reflecting its scale as a Book and Periodical Publishing.

Neither Bookanory Publishing House nor Mud Puddle Inc. holds SOC 2 Type 1 certification.

Neither Bookanory Publishing House nor Mud Puddle Inc. holds SOC 2 Type 2 certification.

Neither Bookanory Publishing House nor Mud Puddle Inc. holds ISO 27001 certification.

Neither Bookanory Publishing House nor Mud Puddle Inc. holds PCI DSS certification.

Neither Bookanory Publishing House nor Mud Puddle Inc. holds HIPAA certification.

Neither Bookanory Publishing House nor Mud Puddle 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.

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.