Comparison Overview

Dropbox

VS

Example, Inc

Dropbox

1800 Owens St, San Francisco, California, 94158, US
Last Update: 2025-05-06 (UTC)
Between 800 and 900
http://www.dropbox.com

Strong

Dropbox is the one place to keep life organized and keep work moving. With more than 700 million registered users across 180 countries, we're on a mission to design a more enlightened way of working. To learn more about working at Dropbox, visit jobs.dropbox.com We also have a few simple guidelines to keep this space respectful and productive. Please avoid: - Harassing other people or using language that’s hateful, offensive, vulgar, or advocates violence - Trolling, fraud and spamming - Violating someone else’s rights or privacy - Advertising or soliciting donations - Link baiting - Posting off topic comments or thread hijacking We may remove comments that violate these guidelines.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 3,585
Subsidiaries: 0
12-month incidents
0
Known data breaches
3
Attack type number
2

Example, Inc

None
Last Update: 2025-05-14 (UTC)

Strong

Between 800 and 900
https://example.com

None

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 0
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/dropbox.jpeg
Dropbox
—
ISO 27001
Not verified
—
SOC 2
Not verified
—
GDPR
No public badge
—
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Example, Inc
—
ISO 27001
Not verified
—
SOC 2
Not verified
—
GDPR
No public badge
—
PCI DSS
No public badge
Compliance Summary
Dropbox
100%
Compliance Rate
0/4 Standards Verified
Example, Inc
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Dropbox in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Example, Inc in 2025.

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

Dropbox cyber incidents detection timeline including parent company and subsidiaries

Incident History — Example, Inc (X = Date, Y = Severity)

Example, Inc cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/dropbox.jpeg
Dropbox
Incidents

Date Detected: 11/2022
Type:Cyber Attack
Attack Vector: Phishing, Impersonation
Blog: Blog

Date Detected: 11/2022
Type:Breach
Attack Vector: Phishing, Credential Theft
Motivation: Data Theft
Blog: Blog

Date Detected: 10/2016
Type:Breach
Attack Vector: Website, Forum
Blog: Blog
https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Example, Inc
Incidents

Date Detected: 03/2024
Type:Cyber Attack
Attack Vector: MOVEit file transfer system
Blog: Blog

FAQ

Both Dropbox company and Example, Inc company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Dropbox company has faced a higher number of disclosed cyber incidents historically compared to Example, Inc company.

In the current year, Example, Inc company and Dropbox company have not reported any cyber incidents.

Neither Example, Inc company nor Dropbox company has reported experiencing a ransomware attack publicly.

Dropbox company has disclosed at least one data breach, while the other Example, Inc company has not reported such incidents publicly.

Both Example, Inc company and Dropbox company have reported experiencing targeted cyberattacks.

Neither Dropbox company nor Example, Inc company has reported experiencing or disclosing vulnerabilities publicly.

Neither Dropbox company nor Example, Inc company has publicly disclosed detailed information about the number of their subsidiaries.

Dropbox company employs more people globally than Example, Inc company, reflecting its scale as a Software Development.

Latest Global CVEs (Not Company-Specific)

Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in The Wikimedia Foundation MediaWiki Cargo extension allows SQL Injection.This issue affects MediaWiki Cargo extension: 1.39, 1.43, 1.44.

Published
Date
2025-10-17
Updated
Date
2025-10-17
Risk Information
cvss4
Base: 2.1
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/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:N/AU:Y/R:U/V:C/RE:M/U:Amber
References
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki QuizGame extension allows Stored XSS.This issue affects MediaWiki QuizGame extension: 1.39, 1.43, 1.44.

Published
Date
2025-10-17
Updated
Date
2025-10-17
Risk Information
cvss4
Base: 2.0
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/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:N/AU:N/R:U/V:C/RE:M/U:Amber
References
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki PollNY extension allows Stored XSS.This issue affects MediaWiki PollNY extension: 1.39, 1.43, 1.44.

Published
Date
2025-10-17
Updated
Date
2025-10-17
Risk Information
cvss4
Base: 2.0
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/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:N/AU:N/R:U/V:C/RE:M/U:Amber
References
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki WebAuthn extension allows Stored XSS.This issue affects MediaWiki WebAuthn extension: 1.39, 1.43, 1.44.

Published
Date
2025-10-17
Updated
Date
2025-10-17
Risk Information
cvss4
Base: 5.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:H/VA:H/SC:N/SI:N/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:N/R:U/V:C/RE:L/U:Amber
References
Description

pyquokka is a framework for making data lakes work for time series. In versions 0.3.1 and prior, the FlightServer class directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation in the do_action() method. The vulnerable code is located in pyquokka/flight.py at line 283 where arbitrary data from Flight clients is directly passed to pickle.loads(). When FlightServer is configured to listen on 0.0.0.0, this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs action. Additional vulnerability points exist in the cache_garbage_collect, do_put, and do_get functions where pickle.loads is used to deserialize untrusted remote data.

Published
Date
2025-10-17
Updated
Date
2025-10-17
Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References