Dropbox Watchdog

Search issues

Search the Dropbox Watchdog archive

All issues

CVE-2024-5924: a Mark-of-the-Web bypass in the Dropbox Windows app

2024

MediumStatus: ResolvedProduct: Dropbox desktop (Windows)Year: 2024

A tracked vulnerability in the Dropbox desktop application for Windows could strip the 'Mark of the Web' flag from synced files, weakening a key warning that protects users from running downloaded, untrusted content.

What happened

Windows attaches a 'Mark of the Web' (MOTW) tag to files that originate from the internet. That tag is what triggers SmartScreen reputation checks and the 'this file came from another computer' protections, and what makes Office open risky documents in Protected View. CVE-2024-5924 describes a flaw in the Dropbox desktop application for Windows whereby files arriving through Dropbox sync could be written without the MOTW flag, effectively laundering an internet-sourced file into one Windows treats as local and trusted.

MOTW-bypass bugs are valuable to attackers because they neutralize a layer of defense that many phishing and malware-delivery chains depend on a victim ignoring. A shared Dropbox folder or link that silently delivered files without the warning could make a malicious document or installer look safer than it is. Public vulnerability trackers list the issue as addressed in current versions of the Dropbox client, so the practical fix is keeping the desktop app up to date.

The entry is included not because it was a mass-exploitation event, but because a serious record of Dropbox's problems should track the concrete, identifier-bearing security defects in its software — not only the headline breaches.

Impact

MOTW bypasses are a recurring target across many applications precisely because they erode a default Windows safeguard. For an app whose entire purpose is moving files between machines and people, silently dropping the 'came from the internet' flag is a meaningful weakening of the security a user reasonably expects. The fix being shipped in updated clients also highlights the importance of auto-updates for desktop sync software.

Dropbox's Response / Official Position

The vulnerability is tracked publicly with a CVE identifier and listed as remediated in current Dropbox desktop releases; Dropbox addresses client security issues through application updates. No detailed public post-mortem specific to this CVE is on the record.

Sources

Related guides

Spot an error, or have a source to add?
Report an error / suggest update

Related issues

9 sources
HighApproximately 5,000 accounts; files accessed in fewer than a third (about 1,500 by 9to5Mac's arithmetic)

The 2026 Lenovo ID sign-in flaw: ~5,000 Dropbox accounts entered without a Dropbox password

A flaw in how Lenovo verified account-holder email addresses let an attacker register a Lenovo ID on a victim's email, and Dropbox's Lenovo ID sign-in link then trusted that identity without ever asking for a Dropbox password — reaching roughly 5,000 accounts.

Security Incidents & Data BreachesCurrent / Ongoing Issues (2024–2026)
Read documentation

Across multiple years, attackers have built convincing fake Dropbox login pages — reached via PDF lures and redirect chains through trusted cloud storage — to harvest victims' real business email and Dropbox credentials.

Security Incidents & Data BreachesAccount Lockouts & Support Failures
Read documentation

ConsentFix, an OAuth-consent phishing technique first documented by Push Security in December 2025 and reported on independently through mid-2026, delivers its Microsoft 365 lures through trusted file-hosting platforms — reporting names both Dropbox and DocSend (a Dropbox company) as hosts for the password-protected files attackers use to get past mail filters.

Security Incidents & Data BreachesCurrent / Ongoing Issues (2024–2026)
Read documentation
2 sources
Medium

2026 root-certificate change forces SDK upgrades or apps lose API access

Because some official Dropbox SDKs pinned root certificates, Dropbox's switch to a new certificate root starting 1 January 2026 means apps on the Java, .NET, or Python SDK must upgrade to specific minimum versions or lose access to the API.

Current / Ongoing Issues (2024–2026)Developer, API & Platform
Read documentation