Comparison Overview
Atypon

Atypon
111 River St, Hoboken, 07030, US
Last Update: 25/02/2026
Atypon develops publishing technologies for getting mission critical content into the hands of the practitioners and researchers who need it most. Literatum, our online publishing and website development platform, gives content providers easy-to-use and automated tools ...

N/A
Last Update: 23/09/2026
The Facebook company is now Meta. Meta builds technologies that help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further empowered billions around t...
Compliance Ranges Comparison

Atypon













Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Atypon in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Facebook in 2026.
Incident History - Atypon (X = Date, Y = Severity)
Atypon cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Facebook (X = Date, Y = Severity)
Facebook cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Atypon

FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.