Comparison Overview
BNP Paribas Ability

BNP Paribas Ability
16, Boulevard des Italiens, Paris, 75009, FR
Last Update: 09/02/2026
Ability est une communauté d'écoute, de partage ouverte à tous les collaborateurs de BNP Paribas, notamment ceux touchés de près ou de loin par les handicaps, les maladies invalidantes ou chroniques. L'objectif étant de développer l'entraide et de faire changer le reg...

alrajhi bank
King Fahad Branch Road, Al Rajhi Tower, Riyadh, Riyadh Province, SA, 11411
Last Update: 04/05/2026
Founded in 1957, Al Rajhi Bank is one of the largest Islamic banks in the world with total assets of SR 384 billion (US$ 102 billion), a paid up capital of SR 25 billion (US$ 6.66 billion) and an employee base of over 9,600 associates. With over 58 years of experience i...
Compliance Ranges Comparison

BNP Paribas Ability







alrajhi bank






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BNP Paribas Ability in 2026.
Incidents vs Banking Industry Avg (This Year)
alrajhi bank has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BNP Paribas Ability (X = Date, Y = Severity)
BNP Paribas Ability cyber incidents detection timeline including parent company and subsidiaries.
Incident History - alrajhi bank (X = Date, Y = Severity)
alrajhi bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BNP Paribas Ability

alrajhi bank
FAQ
Latest Global CVEs
VaahCMS versions 2.0.0 through 2.3.4 contain a malicious obfuscated JavaScript payload embedded in the Blade template responsible for rendering security OTP emails, allowing remote attackers to execute unauthorized code in any browser that renders the affected email template with JavaScript enabled. The payload establishes a WebSocket connection to a hardcoded command-and-control endpoint, installs a password-field keylogger using MutationObserver to capture dynamically added inputs, scrapes WhatsApp Web DOM content, and accepts remote commands to redirect or overwrite the rendered page.
undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. Native Blob objects are safe because their constructor strips CRLF from the type, and fetch is unaffected because it validates headers, but ecosystem libraries that build duck-typed blob shapes from user input can reach the vulnerable path. This is the same defect class as CVE-2022-35948 and CVE-2026-1527, on a header sink that the earlier fixes did not cover. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.
undici's cache interceptor mishandles optional whitespace placed around the equals sign of a qualified no-cache or private Cache-Control directive. In undici from 7.0.0 up to before 7.29.0 and from 8.0.0 up to before 8.9.0, the parser either drops the directive or stores a field name with literal quote characters, so the cache decision fails to recognize the qualification and the response is stored. In shared-cache mode, this lets a response containing one user's authenticated data be served from cache to a later caller, including an unauthenticated one, when both requests resolve to the same cache key. It affects applications that enable the cache interceptor in shared mode, forward Authorization headers upstream, and receive cacheable responses with qualified directives padded with whitespace around the equals sign. This is the whitespace-around-equals variant that the fix for CVE-2026-9678 did not normalize, and it is fixed in undici 7.29.0 and 8.9.0.
kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in check_availability.php via the parameters emailid and email.
- https://github.com/um-dsp/TaintRadar/blob/main/sql_injection_cves/hospitalmanagementsystemproject/20250811-hospital-management-system-check_availability.php-email-sqli/20250811-hospital-management-system-check_availability.php-email-sqli.md
- https://github.com/um-dsp/TaintRadar/blob/main/sql_injection_cves/hospitalmanagementsystemproject/20250811-hospital-management-system-check_availability.php-emailid-sqli/20250811-hospital-management-system-check_availability.php-emailid-sqli.md
kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in /doctor/edit-patient.php?editid=1.