Comparison Overview

Vance Publishing

VS

CRC Press

Vance Publishing

400 Knightsbridge Parkway, Lincolnshire, IL, 60069, US
Last Update: 2025-11-26

Since 1937, Vance Publishing Corporation has established itself as a business information leader within each market it serves. The company has grown organically as well as through strategic acquisitions. As a financially-solid, privately-held enterprise known for attracting the best talent and establishing critical connections with its professional audiences, Vance is in a position to act quickly to meet end-user and marketers’ unique information requirements. As our audiences have taken advantage of multi-platform content opportunities, Vance has significantly invested to ensure that our superior content is available wherever, whenever and however there is an information need. Building on the past 75 years, Vance will continue to invest, and further establish our leadership positions in the customization of content across our platforms; unique, targeted advertising and marketing opportunities; social networks and idea exchanges; and robust, detailed databases. It is with a sense of pride and commitment to our heritage that we serve the agribusiness, beauty, woodworking and home organization industries. I invite you to hear what our employees have to say about the culture at Vance. It is a very exciting time in our history thanks to our employees and their passion for the industries we serve.

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

CRC Press

6000 Broken Sound Parkway, NW, Boca Raton, 33487, US
Last Update: 2025-11-21
Between 750 and 799

CRC Press, a premier global publisher of scientific, technical, and medical content, provides essential material for academics, professionals, and students. CRC Press products include world-class references, handbooks, and textbooks as well as the award-winning CRCnetBASE eBook collections. CRC Press is a member of Taylor & Francis Group, an informa business.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/vance-publishing.jpeg
Vance 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/crc-press.jpeg
CRC Press
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
Vance Publishing
100%
Compliance Rate
0/4 Standards Verified
CRC Press
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 Vance Publishing in 2025.

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

No incidents recorded for CRC Press in 2025.

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

Vance Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — CRC Press (X = Date, Y = Severity)

CRC Press cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/vance-publishing.jpeg
Vance Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/crc-press.jpeg
CRC Press
Incidents

No Incident

FAQ

Both Vance Publishing company and CRC Press company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, CRC Press company has disclosed a higher number of cyber incidents compared to Vance Publishing company.

In the current year, CRC Press company and Vance Publishing company have not reported any cyber incidents.

Neither CRC Press company nor Vance Publishing company has reported experiencing a ransomware attack publicly.

Neither CRC Press company nor Vance Publishing company has reported experiencing a data breach publicly.

Neither CRC Press company nor Vance Publishing company has reported experiencing targeted cyberattacks publicly.

Neither Vance Publishing company nor CRC Press company has reported experiencing or disclosing vulnerabilities publicly.

Neither Vance Publishing nor CRC Press holds any compliance certifications.

Neither company holds any compliance certifications.

CRC Press company has more subsidiaries worldwide compared to Vance Publishing company.

CRC Press company employs more people globally than Vance Publishing company, reflecting its scale as a Book and Periodical Publishing.

Neither Vance Publishing nor CRC Press holds SOC 2 Type 1 certification.

Neither Vance Publishing nor CRC Press holds SOC 2 Type 2 certification.

Neither Vance Publishing nor CRC Press holds ISO 27001 certification.

Neither Vance Publishing nor CRC Press holds PCI DSS certification.

Neither Vance Publishing nor CRC Press holds HIPAA certification.

Neither Vance Publishing nor CRC Press 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.