Comparison Overview
bol

bol
Papendorpseweg 100, Utrecht, 3528 BJ, NL
Last Update: 20/04/2026
Bol is the largest online retailer in the Netherlands and Belgium. In 1999 we opened our virtual doors as first online bookstore in the Netherlands. Nowadays we’re working with 2.000 colleagues to deliver the best shopping platform ever. To be able to do this we have ex...

Lojas Renner S.A.
Av. Joaquim Porto Villanova, 401, Porto Alegre, Rio Grande do Sul, BR, 91410400
Last Update: 02/04/2026
We are a fashion and lifestyle ecosystem connected to our customers through digital channels and more than 600 stores in Brazil, Argentina and Uruguay. From the beginning, everything we do is to enchant. This is how our story began, in 1965, conquering important milesto...
Compliance Ranges Comparison

bol







Lojas Renner S.A.






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
bol has 44.44% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Lojas Renner S.A. in 2026.
Incident History - bol (X = Date, Y = Severity)
bol cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lojas Renner S.A. (X = Date, Y = Severity)
Lojas Renner S.A. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

bol

Lojas Renner S.A.
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.