Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Dropbox Bug Bounty

By Dropbox Bug bounty on Intigriti dropbox.com

Accepting reports Full safe harbor
Go to program
Top reward
$15,000
Top severity paid
Critical
Assets in scope
26
Public CVEs
16
Last change

At a glance

What to know before you start testing.

Pays up to $15,000
for critical bugs, from $100.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Intigriti lists as the payout for each severity.

Severity Reward
Critical $15,000 from $2,000
High $5,000 from $500
Medium $1,000 from $100
Low $500 from $100

Scope

26 assets you may test, 13 excluded.

Wildcard domains 10

  • *.dash.ai
  • *.docsend.com
  • *.dropbox.com
  • *.dropboxer.net
  • *.dropboxforum.com
  • *.dropboxpartners.com
  • *.hellofax.com
  • *.hellosign.com
  • *.helloworks.com
  • *.reclaim.ai

Web 9

  • api.dropbox.com
  • app.Reclaim.ai
  • dash.ai
  • docsend.com
  • Dropbox.com
  • dropbox.com/paper
  • HelloFax.com
  • HelloSign.com
  • sign.dropbox.com

iOS apps 3

  • 1080074001
  • 327630330
  • 6450553960

Android apps 2

  • com.dropbox.android
  • com.dropbox.dash

Products and areas 2

  • dash.dropbox.com
  • Dropbox Desktop Application
Out of scope (13)
  • com.dropbox.paper
  • 1126623662
  • Boxcryptor
  • Dropbox Capture macOS Desktop App
  • Dropbox Capture Windows Desktop App
  • Dropbox Passwords
  • Formswift
  • community-dev.dropbox.com
  • community.dropbox.com
  • community-stage.dropbox.com
  • replay.dropbox.com
  • *.tigrisdata.com
  • *.tigrisdata.io

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Dropbox Bug Bounty (via Intigriti)'s policy. "We" in these lines means the program, not this site.

While testing

  • You may not participate in this program if you are ordinarily resident in, or located in, any country or region subject to comprehensive sanctions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
  • You must be the first reporter of the vulnerability
  • You must not have compromised the privacy of our users or otherwise violated the Dropbox Rules
  • You must not have publicly disclosed the vulnerability prior to the report being closed and permission to disclose granted by the Dropbox team
  • When researching security issues, especially those which may compromise the privacy of others, you must use test accounts in order to respect our users’ privacy.
  • You must comply with all applicable laws in connection with your participation in this program.

Not accepted

  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Same-site scripting

Summarised with AI from the program policy on Intigriti, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 10 minutes ago.

  1. Scope +

    Added to scope: *.tigrisdata.com

  2. Scope +

    Added to scope: *.tigrisdata.io

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope added

    *.tigrisdata.io (out of scope)

  2. Scope added

    *.tigrisdata.com (out of scope)

  3. Status

    Program status changed

  4. Status

    Program status changed

  5. Scope added

    community-dev.dropbox.com (out of scope)

  6. Scope added

    community-stage.dropbox.com (out of scope)

  7. Scope removed

    *.dropbox.com

  8. Scope removed

    community.dropbox.com (out of scope)

  9. Scope removed

    *.dropboxer.net

  10. Scope removed

    Dropbox Capture macOS Desktop App (out of scope)

  11. Scope removed

    *.dropboxpartners.com

  12. Scope removed

    *.helloworks.com

  13. Scope removed

    Formswift (out of scope)

  14. Scope removed

    *.dropboxforum.com

  15. Scope removed

    *.reclaim.ai

  16. Scope removed

    Dropbox Desktop Application

  17. Scope removed

    Dropbox Capture Windows Desktop App (out of scope)

  18. Scope removed

    HelloSign.com

  19. Scope removed

    sign.dropbox.com

  20. Scope removed

    Dropbox.com

  21. Scope removed

    com.dropbox.paper (out of scope)

  22. Scope removed

    app.Reclaim.ai

  23. Scope removed

    dropbox.com/paper

  24. Scope removed

    327630330

  25. Scope removed

    com.dropbox.android

  26. Scope removed

    api.dropbox.com

  27. Scope removed

    1080074001

  28. Scope removed

    1126623662 (out of scope)

  29. Scope removed

    replay.dropbox.com (out of scope)

  30. Scope removed

    HelloFax.com

  31. Scope removed

    docsend.com

  32. Scope removed

    *.docsend.com

  33. Scope removed

    Dropbox Passwords (out of scope)

  34. Scope removed

    *.hellosign.com

  35. Scope removed

    *.hellofax.com

  36. Scope removed

    Boxcryptor (out of scope)

  37. Scope removed

    1126623662

  38. Scope removed

    dropbox.com/paper

  39. Scope removed

    dash.ai

  40. Scope removed

    com.dropbox.android

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-28809 Medium 6.3 23 Mar 2026
CVE-2024-5924 High 8.8 13 Jun 2024
CVE-2024-25718 Critical 9.8 11 Feb 2024
CVE-2022-4768 Medium 6.3 27 Dec 2022
CVE-2022-26181 High 7.8 28 Feb 2022
CVE-2019-12171 High 7.8 8 Jul 2019
CVE-2018-20819 High 7.8 23 Apr 2019
CVE-2018-20820 Medium 5.5 23 Apr 2019
CVE-2018-12445 Low 3.1 20 Jun 2018
CVE-2018-12446 Low 3.6 20 Jun 2018
CVE-2018-12271 Medium 6.4 13 Jun 2018
CVE-2018-12108 Medium 5.5 11 Jun 2018
CVE-2014-8889 Medium 5.3 26 Sep 2017
CVE-2017-8891 Medium 5.5 10 May 2017
CVE-2017-7448 Medium 5.5 5 Apr 2017
CVE-2010-3354 Medium 6.9 20 Oct 2010

Original policy

Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

Welcome to the Dropbox Bug Bounty program — where your curiosity helps keep millions of users safe. At Dropbox, we take security seriously, and we know the best defenses are built with input from the wider security community. Whether you're diving into our apps, APIs, or backend systems, your expertise plays a critical role in protecting the data people trust us with every day. We reward creativity, precision, and clear reporting — and we’re here to support you along the way. Be sure to check out our scope, rules, and submission guidelines before getting started. Let’s work together to make Dropbox even more secure — one bug at a time.

Rules of engagement

By participating in this program, you agree to:

  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • You may not participate in this program if you are ordinarily resident in, or located in, any country or region subject to comprehensive sanctions, or if you are an individual or entity identified on any applicable sanctions list (including those administered by the US, the EU, the UN, or the UK's OFSI).
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Report Eligibility

Only reports that meet the following requirements are eligible to receive a monetary reward:

  • You must be the first reporter of the vulnerability
  • Sometimes, more than one researcher finds and reports the same issue while we are remediating. The bounty will not be split among duplicate reports.
  • Issues found in alpha or beta products may be rewarded at lower levels due to much lower customer impact
  • Issues that are the same root cause but are reported separately to describe attacks via different vectors may be treated as duplicate submissions.
  • Reports that demonstrate a bypass of a mitigation for a security issue will be handled on a case-by-case basis
  • Inquire about performing limited-scope targeted penetration tests if you have written a tool or found a technique to uncover the same issue on multiple endpoints, or different attack vectors or variants with the same root cause.
  • The vulnerability must demonstrate security impact to a site or application in scope (see above)
  • You must not have compromised the privacy of our users or otherwise violated the Dropbox Rules
  • You must not have publicly disclosed the vulnerability prior to the report being closed and permission to disclose granted by the Dropbox team
  • We must not be legally prohibited from rewarding you
  • When researching security issues, especially those which may compromise the privacy of others, you must use test accounts in order to respect our users’ privacy. Accessing private information of other users, performing actions that may negatively affect Dropbox users (e.g., spam, denial of service), or sending reports from automated tools without verifying them will immediately disqualify the report, and may result in additional steps being taken.

RCE reports should provide the following additional information:

  • Timestamp
  • IP Address
  • Command and Control Infrastructure used
  • Timeline

If the RCE was authenticated please also provide:

  • Email address (Please make sure to use your intigriti.me email alias when registering an account)
  • Session ID

You must comply with all applicable laws in connection with your participation in this program. You are also responsible for any applicable taxes associated with any reward you receive.

We may modify the terms of this program or terminate this program at any time. We won’t apply any changes we make to these program terms retroactively.

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti. Submissions validated outside of this may be awarded a $25 bonus.

Vulnerability Severity Time to validate
Exceptional 2 Working days
Critical 2 Working days
High 5 Working days
Medium 15 Working days
Low 15 Working days

This remains at the discretion of Dropbox to award.

In scope

Domains

  • Any report that can demonstrate security impact to Dropbox assets and domains listed in the program.

Feedback Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:

Program feedback link Please note this form will be checked periodically and should not be used for submission or support queries.

Out of scope

Domains

  • Any domain that is not listed in the Domains section, is out of scope for this program
  • Any domain or application with a public or private planned deprecation plan will not be in-scope for the bug bounty program
  • Any domain that is for development or staging will not be eligible for a bounty

Dropbox Specific

  • Any issues pertaining to third-party AI model abuse should be reported to the AI developer team, for example: https://openai.com/form/model-behavior-feedback
  • Any leaked third-party AI API keys should be reported to the AI developer, for example: https://forms.gle/h8bQ5YKWzXb8FtrQ8
  • Reports about verification tokens in ./well-known/ai-plugin.json
  • Any permissions violations by members of the same organization or team for permissions such as https://help.dropbox.com/security/change-admin-rights or https://help.docsend.com/hc/en-us/articles/360000840594-User-Roles or https://faq.hellosign.com/hc/en-us/articles/360038983232-Reporting-in-the-Admin-Console or any other Dropbox technology not listed explicitly above
  • Any session handling reports that do not prove session persistence after 24 hours (Sessions not being invalidated). Session tokens remain valid for 24 hours by design.
  • Password reset token reuse unless it can be demonstrated to persist after one hour or after password reset.
  • Any sensitive customer data that was uploaded erroneously by that customer
  • Any EXIF related reports that contain images that are stored in the user’s storage location are considered out of scope as Dropbox chooses not to alter the user’s photos.
  • Bypass of URL malware detection
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
  • Reports of broken hyperlinks from Dropbox blog posts, press releases, or support articles
  • Hosting malware/arbitrary content on Dropbox and causing downloads
  • XSS on dropboxusercontent.com is out of scope
  • Use of a known-vulnerable library (without evidence of exploitability)
  • Reports from automated tools or scans
  • Reports of spam (i.e., any report involving ability to send emails without rate limits)
  • Attacks that require attacker app to have the permission to overlay on top of our app (e.g., tapjacking)
  • Presence of autocomplete attribute on web forms
  • Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner)
  • Any report on bypassing our storage limits, user limits, user feature restrictions, etc. is out of scope
  • Any report about DLL hijacking without demonstrating how it gains new privileges is also out of scope
  • We will only accept critical reports in blog.dropbox.com (e.g., RCE). Minor issues that can't impact Dropbox users are out of scope
  • Ability to share links without verifying email
  • Reflected File Download vulnerabilities or any vulnerabilities that let you start a download to the user's computer are out of scope
  • IP/Port Scanning via Dropbox services unless you are able to hit private IPs or Dropbox servers
  • Devices (iOS, android, desktop apps) not getting unlinked on password change
  • Hyperlink injection or any link injection in emails we send
  • Creating multiple accounts using the same email
  • Phishing risk via Unicode/Punycode or RTLO issues
  • Being able to upload files with wrong extension in chooser
  • Editable GitHub wikis
  • 3rd Party Integrations not owned by Dropbox (i.e. Intercom Chat feature)
  • Demo sites and scripts (i.e. apidemos.hellosign.com)
  • Access to Riviera or other jailed environment that doesn't demonstrate escaping the jail will be rewarded on a case-by-case basis.

Application

  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Same-site scripting
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (pingbacks aren't sufficient)
  • Disclosed/misconfigured Google Maps API keys
  • Host header injection without proven impact
  • Reports demonstrating issues with business-only impact (e.g., coupon misuse, discount abuse, or non-security functionality of paid services) are welcome and appreciated; however, they do not qualify as security vulnerabilities. These submissions may receive a low-severity bounty only if Dropbox decides to implement a fix.

General

  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
  • Spam, social engineering, and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
  • Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
  • Reports that state that software is out of date/vulnerable without a proof-of-concept

Mobile

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation
  • Path disclosure in the binary
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions

Severity

This program follows Intigriti's triage standards based on the proof of concept.

How we determine final severity We use CVSS as a starting point for evaluating a vulnerability. However, the final severity also factors in likelihood and the broader security impact. Since CVSS does not capture these considerations well on its own, we adjust accordingly.

FAQ

Where can we get credentials for the app?

Dash.ai for Business Dash no longer requires provisioned credentials from Dropbox. To assess Dash components, sign-up for a free trial of Dropbox and Dropbox Dash at Dash.ai.

Other In-Scope Assets For all other business and professional test accounts, please sign up for the free trial period. Make sure to deactivate your own business test accounts prior to billing.