Comparison Overview
Grupo Boticário

Grupo Boticário
Avenida Doutor Dário Lopes dos Santos 2197, Curitiba, Paraná, BR, 80210-010
Last Update: 04/04/2026
Beleza é o negócio do Grupo Boticário. Para nós, ela se traduz em nossas quatro unidades de negócio com atuação no setor cosmético: O Boticário, Eudora, quem disse, berenice? e The Beauty Box. A beleza também está no empreendedorismo, na sustentabilidade, inovação, étic...

L'Oréal
41, Rue Martre, Paris, FR, 92110
Last Update: 01/04/2026
No.1 Beauty Group Worldwide. No.1 most innovative company in Europe (Fortune's ranking). We are 90K employees across 150 countries on five continents, united by our shared purpose: creating the beauty that moves the world. Our 37 international brands are divided int...
Compliance Ranges Comparison

Grupo Boticário







L'Oréal






Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Grupo Boticário in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for L'Oréal in 2026.
Incident History - Grupo Boticário (X = Date, Y = Severity)
Grupo Boticário cyber incidents detection timeline including parent company and subsidiaries.
Incident History - L'Oréal (X = Date, Y = Severity)
L'Oréal cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Grupo Boticário

L'Oréal
FAQ
Latest Global CVEs
A vulnerability was identified in ealpha072 Student-Management-System up to 01451bd7a2f58cdda07bd0b86e3967582e3ecd08. Affected by this issue is some unknown functionality of the file admin/config.php of the component Administrative Backend. Such manipulation leads to improper authentication. The attack may be performed from remote. The exploit is publicly available and might be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was determined in sgl-project SGLang up to 0.5.11. Affected by this vulnerability is the function data_hash of the component Cache Handler. This manipulation causes denial of service. The attack is restricted to local execution. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
Active IQ Config Advisor version 6.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
A vulnerability was found in crmeb crmeb_java 1.4. Affected is the function RestTemplate.getForEntity of the file crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java of the component base64 Qrcode Endpoint. The manipulation of the argument url results in server-side request forgery. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.