Comparison Overview
Municipalidad de San Isidro
Municipalidad de San Isidro
Calle 21 N° 765 San Isidro, Lima, Lima 27, PE
Last Update: 06/12/2025
San Isidro es, actualmente, un distrito que une a su tradición la modernidad y el progreso. Su gran desarrollo urbano con residencias, edificios multifamiliares, centros comerciales y financieros muestran su arquitectura que incorpora los últimos avances de diseño dando...
Social Security Administration
6401 Security Blvd, Baltimore, 21235, US
Last Update: 02/04/2026
Social Security provides financial protection for our nation’s people, supporting more than 64 million individuals and families. With retirement, disability, and survivors benefits, Social Security is one of the most successful anti-poverty programs in our nation's his...
Compliance Ranges Comparison
Municipalidad de San Isidro
Social Security Administration
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Municipalidad de San Isidro in 2026.
Incidents vs Government Administration Industry Avg (This Year)
Social Security Administration has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Municipalidad de San Isidro (X = Date, Y = Severity)
Municipalidad de San Isidro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Social Security Administration (X = Date, Y = Severity)
Social Security Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Municipalidad de San Isidro
Social Security Administration
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.