Comparison Overview
AXA Wealth

AXA Wealth
N/A
Last Update: 28/03/2026
Looking for AXA Wealth? We've closed our LinkedIn account but you can still get in contact with us via your usual contact. You can continue to read our business updates, including information on the sale of the business, at www.axawealth.co.uk/adviser. If you have a pro...

Banco Davivienda
Avenida Calle 26 68C-61, Bogota, 110931, CO
Last Update: 02/04/2026
En Davivienda creemos en un mundo financiero sin barreras que facilite la vida a las personas, las empresas, las ciudades y municipios. Por esta razón hoy somos más de 19.000 personas innovando y creando cada día soluciones y ofertas exclusivas para 10 millones de clien...
Compliance Ranges Comparison

AXA Wealth







Banco Davivienda






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for AXA Wealth in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Banco Davivienda in 2026.
Incident History - AXA Wealth (X = Date, Y = Severity)
AXA Wealth cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Davivienda (X = Date, Y = Severity)
Banco Davivienda cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AXA Wealth

Banco Davivienda
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.