Comparison Overview
Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies
Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies
PO Box 178, Carlow, CW, IE
Last Update: 03/08/2026
CENTRAL REGISTER of BENEFICIAL OWNERSHIP OF COMPANIES AND INDUSTRIAL AND PROVIDENT SOCIETIES A Statutory Instrument, No 110 of 2019, to establish a Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies (RBO) was recently signed i...
U.S. Department of the Treasury
1500 Pennsylvania Ave NW, Washington, 20005, US
Last Update: 25/08/2026
The Treasury Department is the executive agency responsible for promoting economic prosperity and ensuring the financial security of the United States. The Department is responsible for a wide range of activities such as advising the President on economic and financial ...
Compliance Ranges Comparison
Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies
U.S. Department of the Treasury
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies has 31.03% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
U.S. Department of the Treasury has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies (X = Date, Y = Severity)
Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - U.S. Department of the Treasury (X = Date, Y = Severity)
U.S. Department of the Treasury cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Central Register of Beneficial Ownership of Companies and Industrial and Provident Societies
U.S. Department of the Treasury
FAQ
Latest Global CVEs
WWBN AVideo through commit 9c39d8c8 contains an incomplete authentication bypass in encryptPass.json.php that allows unauthenticated attackers to compute valid HMAC tokens using the public site URL and current time. Attackers can forge authentication tokens by computing hash_hmac with the site's base URL as the key and submit arbitrary passwords to receive encrypted hashes, enabling offline precomputation attacks against stolen password databases.
WWBN AVideo through commit 9c39d8c8 contains a cross-site request forgery vulnerability in the get_domain() and isSameDomain() functions that fail to properly validate referer origins. Attackers can forge requests from sibling subdomains or unparseable long-gTLD origins to perform administrative ObjectYPT writes including live server configuration changes.
WWBN AVideo through 30.0 contains an information disclosure vulnerability in the MobileManager plugin getConfiguration endpoint that returns sensitive configuration data to unauthenticated visitors. Attackers can send an unauthenticated GET request to plugin/MobileManager/getConfiguration.json.php to obtain TLS private key file paths, socket configuration details, platform version, and debug flags enabling further targeted attacks.
WWBN AVideo fails to validate password recovery token expiration in userRecoverPassSave.json.php, allowing attackers to use expired tokens to reset account passwords indefinitely. Attackers who obtain a recovery token can use it at any time to change the target account's password and gain full account access.
WWBN AVideo (current e01e41ecc and earlier) makes three login-time security controls depend solely on the client-supplied User-Agent header. The isAVideoEncoder()/isAVideoMobileApp() checks match HTTP_USER_AGENT against a hardcoded literal ("AVideoEncoder"/"AVideoMobileApp") with no IP check or shared secret. An attacker who submits valid credentials and sets User-Agent: AVideoEncoder bypasses two-factor authentication, skips brute-force captcha escalation, and avoids being recorded in the login/device audit history. No patch is available at the time of publication.