Comparison Overview

Omnidawn Publishing

VS

wandr

Omnidawn Publishing

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

Just as our name suggests—“omni” (in all ways and places) and “dawn” (the first appearance of light)—we publish writing that opens us anew to the myriad ways that language may bring new light, new awareness to us. We began Omnidawn in 2001 because of our belief that lively, culturally pertinent, emotionally and intellectually engaging literature can be of great value, and we wanted to participate in the dissemination of such work. We believe that our society needs small presses so that widely diverse ideas and points-of-view are easily accessible to everyone. Italo Calvino: “… the function of literature is communication between things that are different… because they are different, not blunting but even sharpening the differences between them, following the true bent of written language.”

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

wandr

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

wandr's mission is to find the best adventure travel stories and publish them to the world. We believe in the power of storytelling, and using our stories to encourage people to travel outdoors and experience new adventures. we regularly publish content to our website, and we also offer a paid yearly subscription for those that want to support travel writing and gain access to our interactive digital magazine features. Hey Travel Writers, if you're out there traveling and writing about the natural attractions and adventures that you've found along your journeys, we want to hear from you! We publish first-person narratives that tell a story that will be interesting to our readers!

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
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/omnidawn-publishing.jpeg
Omnidawn 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/wandr.jpeg
wandr
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
Omnidawn Publishing
100%
Compliance Rate
0/4 Standards Verified
wandr
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 Omnidawn Publishing in 2025.

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

No incidents recorded for wandr in 2025.

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

Omnidawn Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — wandr (X = Date, Y = Severity)

wandr cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/omnidawn-publishing.jpeg
Omnidawn Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/wandr.jpeg
wandr
Incidents

No Incident

FAQ

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

Historically, wandr company has disclosed a higher number of cyber incidents compared to Omnidawn Publishing company.

In the current year, wandr company and Omnidawn Publishing company have not reported any cyber incidents.

Neither wandr company nor Omnidawn Publishing company has reported experiencing a ransomware attack publicly.

Neither wandr company nor Omnidawn Publishing company has reported experiencing a data breach publicly.

Neither wandr company nor Omnidawn Publishing company has reported experiencing targeted cyberattacks publicly.

Neither Omnidawn Publishing company nor wandr company has reported experiencing or disclosing vulnerabilities publicly.

Neither Omnidawn Publishing nor wandr holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Omnidawn Publishing company nor wandr company has publicly disclosed detailed information about the number of their subsidiaries.

Omnidawn Publishing company employs more people globally than wandr company, reflecting its scale as a Book and Periodical Publishing.

Neither Omnidawn Publishing nor wandr holds SOC 2 Type 1 certification.

Neither Omnidawn Publishing nor wandr holds SOC 2 Type 2 certification.

Neither Omnidawn Publishing nor wandr holds ISO 27001 certification.

Neither Omnidawn Publishing nor wandr holds PCI DSS certification.

Neither Omnidawn Publishing nor wandr holds HIPAA certification.

Neither Omnidawn Publishing nor wandr 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.