Comparison Overview

TOTVS

VS

Meta

TOTVS

Av Braz Leme, 1000, Sao Paulo, 02511-900, BR
Last Update: 2026-01-18
View Profile
Between 750 and 799
https://www.totvs.com

Olá, somos a TOTVS! A maior empresa de tecnologia do Brasil. 🤓 Líder absoluta em sistemas e plataformas para empresas, a TOTVS possui mais de 70 mil clientes. Indo muito além do ERP, oferece tecnologia completa para digitalização dos negócios por meio de 3 unidades de negócio: - Gestão: ERPs, soluções cross e sistemas especializados visando garantir mais produtividade, eficiência e governança para os negócios; 💻 - Techfin: ERP Banking que oferece soluções de crédito B2B e pagamento, integrados a sistemas de gestão; 💸 - RD Station: Ferramentas digitais de marketing, vendas e relacionamento, para empresas de todos os portes e segmentos. 🚀 Nos últimos 5 anos, a companhia investiu R$3 bilhões em pesquisa e desenvolvimento para atender de maneira cada vez mais especializada empresas de 12 segmentos da economia, tornando-se um trusted advisor de seus clientes. A TOTVS é uma potência tecnológica que apoia a evolução de empresas de norte a sul do país. O Brasil, que faz, faz com TOTVS.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 16,566
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Meta

1 Hacker Way, Menlo Park, CA, US, 94025
Last Update: 2026-01-21
Between 700 and 749
https://www.metacareers.com/

Meta's mission is to build the future of human connection and the technology that makes it possible. Our technologies help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further empowered billions around the world. Now, Meta is moving beyond 2D screens toward immersive experiences like augmented and virtual reality to help build the next evolution in social technology. To help create a safe and respectful online space, we encourage constructive conversations on this page. Please note the following: • Start with an open mind. Whether you agree or disagree, engage with empathy. • Comments violating our Community Standards will be removed or hidden. Please treat everybody with respect. • Keep it constructive. Use your interactions here to learn about and grow your understanding of others. • Our moderators are here to uphold these guidelines for the benefit of everyone, every day. • If you are seeking support for issues related to your Facebook account, please reference our Help Center (https://www.facebook.com/help) or Help Community (https://www.facebook.com/help/community). For a full listing of our jobs, visit https://www.metacareers.com

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 146,293
Subsidiaries: 21
12-month incidents
1
Known data breaches
13
Attack type number
4

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/totvs.jpeg
TOTVS
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/meta.jpeg
Meta
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
TOTVS
100%
Compliance Rate
0/4 Standards Verified
Meta
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for TOTVS in 2026.

Incidents vs Software Development Industry Average (This Year)

Meta has 17.36% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incident History — TOTVS (X = Date, Y = Severity)

TOTVS cyber incidents detection timeline including parent company and subsidiaries

Incident History — Meta (X = Date, Y = Severity)

Meta cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/totvs.jpeg
TOTVS
Incidents

No Incident

https://images.rankiteo.com/companyimages/meta.jpeg
Meta
Incidents

Date Detected: 1/2026
Type:Cyber Attack
Attack Vector: Phishing Email
Motivation: Identity Fraud, Data Theft, Scam Distribution
Blog: Blog

Date Detected: 1/2026
Type:Breach
Attack Vector: API Vulnerability Exploitation, Third-Party Scraping
Motivation: Data Exfiltration for Financial Gain, Identity Theft, Phishing Campaigns
Blog: Blog

Date Detected: 12/2025
Type:Vulnerability
Attack Vector: Unsafe deserialization of payloads
Motivation: Exploitation for remote code execution, potential data exfiltration, and botnet integration
Blog: Blog

FAQ

TOTVS company demonstrates a stronger AI Cybersecurity Score compared to Meta company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Meta company has historically faced a number of disclosed cyber incidents, whereas TOTVS company has not reported any.

In the current year, Meta company has reported more cyber incidents than TOTVS company.

Neither Meta company nor TOTVS company has reported experiencing a ransomware attack publicly.

Meta company has disclosed at least one data breach, while TOTVS company has not reported such incidents publicly.

Meta company has reported targeted cyberattacks, while TOTVS company has not reported such incidents publicly.

Meta company has disclosed at least one vulnerability, while TOTVS company has not reported such incidents publicly.

Neither TOTVS nor Meta holds any compliance certifications.

Neither company holds any compliance certifications.

Meta company has more subsidiaries worldwide compared to TOTVS company.

Meta company employs more people globally than TOTVS company, reflecting its scale as a Software Development.

Neither TOTVS nor Meta holds SOC 2 Type 1 certification.

Neither TOTVS nor Meta holds SOC 2 Type 2 certification.

Neither TOTVS nor Meta holds ISO 27001 certification.

Neither TOTVS nor Meta holds PCI DSS certification.

Neither TOTVS nor Meta holds HIPAA certification.

Neither TOTVS nor Meta holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References