Comparison Overview
Communication Research Center at Boston University

Communication Research Center at Boston University
704 Commonwealth Ave, Boston, Massachusetts, 02215, US
Last Update: 02/04/2026
The Communication Research Center (CRC) at Boston University is the College of Communication’s (COM’s) media research hub. Research is an integral part of faculty and student activities at BU. Researchers at COM use the most advanced theory and methods to examine commun...

Utrecht University
Heidelberglaan 6, Utrecht, Utrecht, 3512, NL
Last Update: 02/04/2026
At Utrecht University (UU), we are working towards a better world. We do this by researching complex issues beyond the borders of disciplines. We put thinkers in contact with doers, so new insights can be applied. We give students the space to develop themselves. In so ...
Compliance Ranges Comparison

Communication Research Center at Boston University







Utrecht University






Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Communication Research Center at Boston University in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Utrecht University in 2026.
Incident History - Communication Research Center at Boston University (X = Date, Y = Severity)
Communication Research Center at Boston University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Utrecht University (X = Date, Y = Severity)
Utrecht University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Communication Research Center at Boston University

Utrecht University
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.