Banner object (1)

Hack and Take the Cash !

805 bounties in database
  Back Link to program      
Tumblr logo
Hall of Fame



Welcome to Tumblr

The Tumblr Bug Bounty Program was designed for those security-conscious users who help keep the Tumblr community safe from criminals and jerks. If you submit a bug that is within the scope of the program (as defined below), we will gladly reward you for your keen eye. Also, by submitting you agree that your submissions are subject in relevant part to Tumblr’s Application Developer and API License Agreement.

The security of Tumblr and our users is always a top priority for us. We look forward to working with the security community and invite security researchers to report security vulnerabilities that are identified in our products.

Table of Contents

  • Rules of Engagement
    1. Program Rules
    2. Legal Terms
    3. Safe Harbor
  • Responsible Disclosure of Vulnerabilities
    1. Testing
    2. SSRF Server
    3. Crafting a Report
    4. Same Bug, Different Host
    5. Same Payload, Different Parameter
    6. Program Scope
  • Rewards
    1. Payout Table
    2. Vulnerability Priority Baselines
    3. Borderline Out-of-Scope, No Bounty
    4. Do Not Report

Rules of Engagement

By submitting reports or otherwise participating in this program, you agree that you have read and will follow the Program Rules and Legal Terms sections of this program Policy.

Program Rules

Violation of any of these rules can result in ineligibility for a bounty and/or removal from the program. Three strikes will earn you a temporary ban. Four strikes means a permanent ban.

  1. Test vulnerabilities only against accounts that you own or accounts that you have permission from the account holder to test against.
  2. Never use a finding to compromise/exfiltrate data or pivot to other systems. Use a proof of concept only to demonstrate an issue.
  3. If sensitive information--such as personal information, credentials, etc.--is accessed as part of a vulnerability, it must not be saved, stored, transferred, accessed, or otherwise processed after initial discovery. All copies of sensitive information must be returned to Tumblr and may not be retained.
  4. Researchers may not, and are not authorized to engage in any activity that would be disruptive, damaging or harmful to Tumblr or its users. This includes: social engineering, phishing, physical security and denial of service attacks against users, employees, or Tumblr as a whole.
  5. Abide by the program scope. Only reports submitted to this program and against assets in scope will be eligible for monetary award.
  6. Researchers may not publicly disclose vulnerabilities (sharing any details whatsoever with anyone other than authorized Tumblr employees), or otherwise share vulnerabilities with a third party, without Tumblr’s express written permission.

Legal Terms

In connection with your participation in this program you agree to comply with Tumblr’s Terms of Service, Tumblr’s Privacy Policy, and all applicable laws and regulations, including including any laws or regulations governing privacy or the lawful processing of data.

Tumblr reserves the right to change or modify the terms of this program at any time. You may not participate in this program if you are a resident or individual located within a country appearing on any U.S. sanctions lists (such as the lists administered by the US Department of the Treasury’s OFAC).

Tumblr does not give permission/authorization (either implied or explicit) to an individual or group of individuals to (1) extract personal information or content of Tumblr users or publicize this information on the open, public- facing internet without user consent or (2) modify or corrupt programs or data belonging to Tumblr in order to extract and publicly disclose data belonging to Tumblr.

Tumblr employees, contingent workers, contractors and their personnel, and consultants, as well as their immediate family members and persons living in the same household, are not eligible to receive bounties or rewards of any kind under any Tumblr programs, whether hosted by Tumblr or any third party.

Safe Harbor

Tumblr will not initiate a lawsuit or law enforcement investigation against a researcher in response to reporting a vulnerability if the researcher fully complies with this Policy.

Please understand that if your security research involves the networks, systems, information, applications, products, or services of another party (which is not us), that third party may determine whether to pursue legal action. We cannot and do not authorize security research in the name of other entities. If legal action is initiated by a third party against you and you have complied with this Policy, we will take reasonable steps to make it known that your actions were conducted in compliance with this Policy.

You are expected, as always, to comply with all applicable laws and regulations.

Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this Policy.

Responsible Disclosure of Vulnerabilities

We are continuously working to evolve our bug bounty program. We aim to respond to incoming submissions as quickly as possible and make every effort to have bugs fixed within 90 days of being triaged.

Please review the program scope before submitting a report.


Web traffic to and from Tumblr produces vast amounts of data every day. When testing, you can make it easier for us to identify your testing traffic against our normal data and the malicious actors out in the world. Please do one or both of the following when participating in the Tumblr bug bounty program:

  • Where possible, register accounts using your <username> addresses. This is not a requirement for eligibility but will help for identification purposes.
  • Provide your IP address in the bug report. We will keep this data private and only use it to review logs related to your testing activity.
  • Include a custom HTTP header in all your traffic. Burp and other proxies allow the easy automatic addition of headers to all outbound requests. Report to us what header you set so we can identify it easily. For example:
    • A header that includes your username: X-Bug-Bounty:HackerOne-<username>
    • A header that includes a unique or identifiable flag X-Bug-Bounty:ID-<sha256-flag>
  • Target our internal SSRF Server (see below) for any SSRF tests

When testing for a bug, please also keep in mind:

  • Only use authorized accounts so as not to inadvertently compromise the privacy of our users
  • When attempting to demonstrate root permissions with the following primitives in a vulnerable process please use the following commands:
    • Read: cat /proc/1/maps
    • Write: touch /root/<your H1 username>
    • Execute: id, hostname, pwd (though, technically cat and touch also prove execution)
  • Minimize the mayhem. Adhere to program rules at all times. Do not use automated scanners/tools - these tools include payloads that could trigger state changes or damage production systems and/or data.
  • Before causing damage or potential damage: Stop, report what you've found and request additional testing permission.

SSRF Server

When testing for Server Side Request Forgery (SSRF), we've set up a server inside our network that you can use for verifying SSRF vulnerabilities. It has the following assets you can target:

Crafting a Report

If our security team cannot reproduce and verify an issue, a bounty cannot be awarded. To help streamline our intake process, we ask that submissions include:

  • Description of the vulnerability
  • Steps to reproduce the reported vulnerability
  • Proof of exploitability (e.g. screenshot, video)
  • Perceived impact to another user or the organization
  • Proposed CVSSv3 __Vector& Score (without environmental and temporal modifiers)
  • List of URLs and affected parameters
  • Other vulnerable URLs, additional payloads, Proof-of-Concept code
  • Browser, OS and/or app version used during testing

Note: Failure to adhere to these minimum requirements may result in the loss of a reward.

All supporting evidence and other attachments must be stored only within the report you submit. Do not host any files on external services.

Same Bug, Different Host

For each report, please allow Tumblr sufficient time to patch other host instances. If you find the same bug on a different (unique) host, prior to the report reaching a triaged state, file it within the existing report. Any reports filed separately while we are actively working to resolve the issue will be treated as a duplicate.

Same Payload, Different Parameter

In some cases, rewards may be consolidated into a single payout. For example, multiple reports of the same vulnerability across different parameters of a resource, or demonstrations of multiple attack vectors against a fundamental framework issue. We kindly ask you to consolidate reports rather than separate them.

Program Scope

Please see our detailed scope list at the bottom of this page for a full list of assets that are out of scope. This list is subject to change without notice.

If you’ve found a vulnerability that affects an asset belonging to Tumblr, but is not outlined in the in scope section of this program and isn't excluded either, please report it to this program and we will review.


You will be eligible for a bounty only if you are the first person to disclose an unknown issue. Qualifying bugs will be rewarded based on severity, to be determined by Tumblr in its sole discretion. Rewards may range from HackerOne Reputation Points to monetary rewards up to $5,000 USD. Awards are granted entirely at the discretion of Tumblr.

At Tumblr's discretion, providing more complete research, proof-of-concept code and detailed write-ups may increase the bounty awarded. Conversely, Tumblr may pay less for vulnerabilities that require complex or over- complicated interactions or for which the impact or security risk is negligible. Rewards may be denied if there is evidence of program policy violations. A reduction in bounty is also warranted for reports that require specific browser configurations.

Payout Table

Where a monetary bounty is presented, eligible reports will be awarded based on severity after identifying final impact, as determined by Tumblr.

Severity | Payout Range
Critical | $1,000 - $5,000
High | $500 - $1,000
Medium | $100 - $500
Low | $100
None | $0

Vulnerability Priority Baselines

All reports will be awarded based on their actual impact and severity which will be determined by Tumblr in its sole discretion.

As a general guide to vulnerability priority baselines, one resource that we suggest to check out is this Vulnerability Rating Taxonomy __. This only serves as a guide and does not guarantee actual report classification.

Borderline Out-of-Scope, No Bounty

These issues are eligible for submission, but not eligible for bounty or any award. Once triaged, they will be closed as Informative only if found to be valid or Spam if found to be not valid. When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

Issues: |
Any non-Tumblr Applications | "Self" XSS
Missing Security Best Practices | HTTP Host Header XSS
Confidential Information Leakage | Clickjacking/UI Redressing
Use of known-vulnerable library (without proof of exploitability) | Intentional Open Redirects
Missing cookie flags | Reflected file download
SSL/TLS Best Practices | Incomplete/Missing SPF/DKIM
Physical attacks | Social Engineering attacks
Results of automated scanners | Login/Logout/Unauthenticated CSRF
Autocomplete attribute on web forms | Using unreported vulnerabilities
Issues related to networking protocols | Software Version Disclosure
Verbose error pages (without proof of exploitability) | Denial of Service attacks
Tumblr software that is End of Life or no longer supported | Account/email Enumeration
Missing Security HTTP Headers (without proof of exploitability) | Internal pivoting, scanning, exploiting, or exfiltrating data

Note: 0-day vulnerabilities may be reported 30 days after initial publication. We have an internal process dedicated to tracking these issues; hosts identified by this process and internally ticketed will not be eligible for bounty.

Do Not Report

The following issues are considered out of scope:

  • Those that resolve to third-party services
  • Issues that do not affect the latest version of modern browsers
  • Issues that we are already aware of or have been previously reported
  • Issues that require unlikely user interaction
  • Disclosure of information that does not present a significant risk
  • Cross-site Request Forgery with minimal security impact
  • CSV injection
  • Incomplete or missing SPF/DKIM
  • General best practice concerns

In Scope

Scope Type Scope Name
  • Minimum OS version: API 21
  • Certificate pinning
  • API keys in code
  • Minimum OS version: iOS 11
  • Certificate pinning
  • API keys in code


  • Header: X-tumblr-user can be used to identify if the domain is a blog on the Blog Network
  • View the domain in a browser, there will be a Tumblr banner visible.
  • JavaScript is allowed; XSS is excluded from eligibility.
  • Pages can be framed; Clickjacking or other X-Frame-Options attacks are excluded from eligibility.















This program have been found on Hackerone on 2019-10-02.

FireBounty © 2015-2020

Legal notices