- Top reward
- $10,000
- Top severity paid
- Critical
- Assets in scope
- 10
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $10,000
- for critical bugs, from $50.
- Report on Bugcrowd
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- Public disclosure allowed
- You may publish your report.
Rewards
What Bugcrowd lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$10,000 from $650 |
| High |
|
$5,000 from $450 |
| Medium |
|
$800 from $200 |
| Low |
|
$200 from $50 |
Earlier reward tables (1)
- 11 Nov 2026 to 11 Nov 2026: Critical up to $10,000
Scope
10 assets you may test, 1 excluded.
Web 5
- https://blog.etsy.com
- https://careers.etsy.com
- https://community.etsy.com
- https://help.etsy.com
- https://www.etsy.com
Android apps 1
- https://www.etsy.com/mobile
APIs 1
- https://www.etsy.com/developers/documentation/getting_started/api_basics
iOS apps 1
- https://www.etsy.com/mobile
Wildcard domains 1
- *.etsy.com
Products and areas 1
- https://etsypayments.com
Out of scope (1)
- icht.etsysecure.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Etsy (via Bugcrowd)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please use your @bugcrowdninja.com email address when creating testing account(s).
-
Please only perform testing against accounts you expressly own and control.
-
Please don't create an excessive number of accounts for testing, and please limit your test transactions to small monetary amounts (like ~$1).
-
If you'd like to test convos, please use dedicated test accounts only and do not message legitimate members of the site.
-
Avoid using site-wide scanners.
-
DO NOT use automated scanners when testing etsypayments.com .
-
Putting your shop in developer mode hides your shop and listings in our search functionality.
-
researchers should not pull, change, or erase any customer data during testing.
Not accepted
-
Security reports that don't pertain to etsy.com
-
Flaws specific to out of date browsers/plugins.
-
Simple, non-XSS content injection.
-
Logout cross-site request forgery.
-
Lack of the Secure flag on non-sensitive cookies.
-
Lack of HTTPOnly flag on non-sensitive cookies.
-
Username enumeration through login or password reset.
-
CSRF issues submitted with a proof-of-concept containing a nonce.
Summarised with AI from the program policy on Bugcrowd, 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.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
icht.etsysecure.com (out of scope)
-
Scope added
*.etsy.com
-
Scope added
https://community.etsy.com
-
Scope added
https://help.etsy.com
-
Scope added
https://careers.etsy.com
-
Scope added
https://blog.etsy.com
-
Scope added
https://etsypayments.com
-
Scope added
https://www.etsy.com/mobile
-
Scope added
https://www.etsy.com
Public CVEs
Published vulnerabilities in this vendor's products, from the 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 bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
Program Overview Etsy is the global marketplace for unique and creative goods, connecting millions of buyers and sellers around the world. Through our marketplace and seller tools, we help creative entrepreneurs start, manage, and grow their businesses. Our mission is simple: Keep Commerce Human . Our bug bounty program has been running since 2012, and it remains an important part of how we protect the Etsy community. We partner with security researchers who practice responsible disclosure and help us identify vulnerabilities that could impact the safety, trust, and resilience of our marketplace. If you discover a valid security issue, we want to hear from you. Please use your @bugcrowdninja.com email address when creating testing account(s). To protect the integrity of the program, we reserve the right to suspend, delete, or block any test accounts that violate our testing guidelines. Vulnerability Guidelines & Exceptions Vulnerability reports MUST have a proof of concept or detailed explanation of the security issue. Please note the Vulnerability Exceptions section for a list of vulnerabilities which are NOT accepted. Higher quality reproduction steps and reports will be a strong factor in determining a valid issue's final bounty reward amount (In general, better reports -> bigger bounty reward). PLEASE provide clear step-by-step for replication. Rewards This program adheres to the Bugcrowd Vulnerability Rating Taxonomy for the prioritization/rating of findings. Changes to VRT priorities for certain bugs are listed below: VRT Adjustments VRT Category │ Adjusted Value No Rate Limiting on Form - Login │ P5 No Rate Limiting on Form - email triggering │ P5 Cross-Site Scripting - IE-only/older version │ P5 Username Enumeration │ P5 No Password Policy │ P5
Targets
Any domain/property of Etsy not listed in the targets section is out of scope. This includes any/all domains not listed above. Focus Areas This program is focused on vulnerabilities in Etsy's mobile & web applications. These applications are used by Etsy customers and sellers. Additionally, the developer APIs and portal is also in-scope. Unauthenticated access to users' accounts / information, especially PII (Personally Identifiable Information). Developer API vulnerabilities. Production Environment: Please note that this program scope is a production environment. With that in mind, please be sure to avoid harming infrastructure, interacting with customers, and attempting to access, manipulate, and/or attack accounts you do not explicitly own. Access & Credentials: All in-scope target applications are publicly accessible. Credentials can be self-provisioned as needed. Please only perform testing against accounts you expressly own and control. Buyer and Seller Accounts Seller Shop Sign-Up: https://www.etsy.com/your/shop/create?us_sell_create_value Please Note: when registering a Seller Shop, there is identity verification. Buyer Sign-Up: https://www.etsy.com Testing payment/purchasing flow: Create a seller account, selling something for $1 Create a buyer account, buying the item for $1 As the seller, refund the purchase NOTE: there is a 20 cent fee (on a $1 purchase) associated with transactions for sellers - this cannot be reimbursed by Etsy. Please be cognizant of this and test accordingly. ------ #### Third Party Bugs Etsy uses a number of third-party providers and services. We cannot authorize security testing against systems that do not belong to us, but strongly suggest reporting issues identified within these services to the third-party directly. However, if you believe an issue with one of our third-party service providers is the result of Etsy's misconfiguration or insecure usage of that service (or you've reported an issue affecting many customers of the service that you believe Etsy can temporarily mitigate without stopping usage of the service while a fix is implemented upstream), we'd appreciate your report regarding the issue. Keep in mind that any reports regarding third-party services are rewarded on a case-by-case basis. Target Information Mobile Applications Android: https://play.google.com/store/apps/details?id=com.etsy.android&hl=en iPhone: https://itunes.apple.com/us/app/etsy-shop-creative/id477128284?mt=8 Etsy API (v3) Documentation for the Etsy API: https://www.etsy.com/developers/documentation If you're interested in testing listings or other shop-related functionality, please put your shop in developer mode: https://www.etsy.com/developers/shop etsypayments.com Applicable to credit card and gift card payments. This is a secure payment method storage system that interacts with buyer and shop accounts. Documentation is not provided. help.etsy.com Primarily interested in findings introduced by Etsy customizations Zendesk-wide bugs will be accepted on a case-by-case basis Testing Guidelines: Set your shop to developer mode here: https://www.etsy.com/developers/shop (after you register an account and complete seller onboarding). Putting your shop in developer mode hides your shop and listings in our search functionality. Please don't create an excessive number of accounts for testing, and please limit your test transactions to small monetary amounts (like ~$1). If you'd like to test convos, please use dedicated test accounts only and do not message legitimate members of the site. If testing the listing process, ensure your shop is in developer mode (see above) Avoid using site-wide scanners. Researchers should be using targeted scanning tools as to prevent affecting the production environment. Testing Payments Be mindful with the rate and scope of automated scanning tools. DO NOT use automated scanners when testing etsypayments.com . Account Freezes: there are situations where during testing your account may be frozen due to fraud protection measures. If this happens, please reach out to the Bugcrowd Support Portal. ------ Vulnerability Exceptions Security reports that don't pertain to etsy.com If you're sending in a report for a domain that is not covered in the scope of our bug bounty program, we will ignore it. Flaws specific to out of date browsers/plugins. Learn more about up-to-date browsers here . Simple, non-XSS content injection. Manipulating a URL to present a page that contains custom text does not qualify for the bug bounty program. Logout cross-site request forgery. For more information on this issue, please refer to blog posts on the topic by Chris Evans and Michal Zalewski . Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies. More information on this is available here: http://codeascraft.com/2012/10/09/scaling-user-security/ . Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability. Username enumeration through login or password reset. While username enumeration can be a vulnerability in a number of web applications, Etsy is a public marketplace and as such usernames can be enumerated by design through a number of ways including listings, forum posts, shops, etc. CSRF issues submitted with a proof-of-concept containing a nonce. Out-of-Scope DoS/DDoS 3rd party systems and solutions (any resource / service not managed by Etsy). Spam or any other mass distribution to customers, partners, etc. Pulling / manipulating any user data or user accounts - during testing, researchers should not pull, change, or erase any customer data during testing. Customer support channels (chat, phone, email, etc.) - If you have any questions or issues while testing, please send an email to [email protected]. Testing is only authorized on the targets listed as In-Scope. Any domain/property of Etsy not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in-scope, but that demonstrably belongs to Etsy, it may be reported to this program, and is appreciated - but will ultimately be marked as 'not applicable' and will not be eligible for monetary or points-based compensation.
In Scope (in scope)
These targets are backed by third party services. Only bugs that are the result of a misconfiguration on Etsy's part are in scope.
In Scope (in scope)
For subdomains hosted by third party services, only misconfigurations on Etsy's part will be accepted.