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

Flickr

Bug bounty on HackerOne flickr.com

Accepting reports Full safe harbor
Go to program Website
Top reward
$8,500
Top severity paid
Critical
Assets in scope
5
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $8,500
for critical bugs.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 3 days
As the policy promises.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $8,500 from $5,000
High $4,000 from $2,000
Medium $700 from $300
Low $300 from $100
Response
Within 3 days Time to first response (from report submit) - 3 business days
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

5 assets you may test, 17 excluded.

Web 2

  • modefestival.com Critical
  • www.whatismode.com Critical

Android apps 1

  • com.yahoo.mobile.client.android.flickr Critical

iOS apps 1

  • 328407587 Critical

Wildcard domains 1

  • *.flickr.com Critical
Out of scope (17)
  • Zero Day Vulnerabilities/Security Upgrades
  • amt.flickr.com
  • appletv.flickr.com
  • blog.flickr.com
  • blogtest.flickr.com
  • bluebird.flickr.com
  • code.flickr.com
  • csp.flickr.com
  • flickrhelp.com
  • guce.flickr.com
  • health.flickr.com
  • help.flickr.com
  • links.flickr.com
  • parkorbird.flickr.com
  • stage.guce.flickr.com
  • trunk.guce.flickr.com
  • *.flickr.net

Rules

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

While testing

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • Please only submit bugs that show a clear exploit, not a theoretical vector

Not accepted

  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Self XSS
  • Spam
  • Reports of exposed hostnames or IPs without any actual exploit
  • Anything related to abuse reporting on our platform.
  • Any issue that results in users being logged out of Flickr, without exposing any PII or allowing for account takeover
  • Any issue related to circumventing free account restrictions (i.e. 1000 photo limit)
  • Anything related to SPF or email configuration
  • Anything related to the sending or receiving of emails, with the exception of email content (i.e. Email header bugs are out of scope)
  • Re-use of our public Weglot translation key

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

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

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

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

Welcome to Flickr's Bug Bounty Program! We look forward to seeing your reports and working with you to improve our product. Please reach out with any questions, and feel free to share a link to your photostream on reports if you're a user of the product. Thanks!

Response Targets

Flickr will make a best effort to meet the following response targets for hackers participating in our program:

  • Time to first response (from report submit) - 3 business days
  • Time to triage (from report submit) - 3 business days
  • Time to bounty (from triage) - 14 business days

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Please only submit bugs that show a clear exploit, not a theoretical vector

Rewards

Please see the structured bounty table above and report criteria below. Our bounty table provides general guidelines, and all final decisions are at the discretion of Flickr.

Report Criteria

To ensure proper assessment, all vulnerability reports must include reproducible steps and a working proof of concept. Demonstrate the vulnerability with specific examples rather than general statements. Reports without these elements will be classified as Informative or Not Applicable.

#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • HTML listed at https://www.flickr.com/html.gne is legitimate usage in text inputs. Clickable links are legitimate usage. Any HTML that’s not outlined at that URL however is fair game.
  • Vulnerabilities that only work on our unsupported browser versions: Chrome, Firefox, Safari, and Edge that are older than the last 2 versions, or any other browser not already listed.
  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Self XSS
  • Spam
  • Vulnerabilities due to user generated content that don't result in access to private data or account takeover (i.e. Links in comments redirecting to a malicious site are out of scope)
  • We're not concerned with keeping our coupon codes secret, please use any you brute-force to buy a subscription :)
  • Reports of exposed hostnames or IPs without any actual exploit
  • Anything related to abuse reporting on our platform. Any Flickr accounts that interfere or submit erroneous abuse reports may be subject to deletion.
  • AWS resources that are not shown to be owned by Flickr
  • Any issue that results in users being logged out of Flickr, without exposing any PII or allowing for account takeover
  • Any issue related to circumventing free account restrictions (i.e. 1000 photo limit)
  • Anything related to SPF or email configuration
  • End-user Flickr API keys leaked on non-Flickr owned GitHub repos, search results, etc.
  • Anything related to the sending or receiving of emails, with the exception of email content (i.e. Email header bugs are out of scope)
  • Re-use of our public Weglot translation key

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Flickr and our users safe!