Hotmart (VDP)
By Hotmart Vulnerability disclosure program on HackerOne hotmart.com
- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 5 days
First Response | 5 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
1 asset you may test, 3 excluded.
Wildcard domains 1
- *.buildstaging.com Critical No bounty
Out of scope (3)
- *ctf*.buildstaging.com
- *.hotmart.com
- *.teachable.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Hotmart (VDP) (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Do not perform tests in a production environment.
-
Only test against assets that are explicitly defined in the scope.
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
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.
-
Do not upload shells or create a backdoor of any kind.
-
No Data deletion / alter is allowed
-
Do not use automated scanners/tools - these tools include payloads that could trigger state changes or damage production systems and/or data.
Not accepted
-
Any activity that could lead to the disruption of our service (DoS or DDoS).
-
Clickjacking
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Self-exploitation (self XSS, self denial-of-service, etc.), unless a method to attack a different user can be demonstrated.
-
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.
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or other 'load testing' types of issues
-
Brute force of promo code
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC/TXT records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
-
Internal IP exposure, unless you can do something impressive with it
-
Leaking information via the Referer header
-
Password or account recovery policies, such as reset link expiration or password complexity
-
Account/email Enumeration
-
Fixed Session
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 3 minutes 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
*ctf*.buildstaging.com (out of scope)
-
Scope added
*.hotmart.com (out of scope)
-
Scope added
*.teachable.com (out of scope)
-
Scope added
*.buildstaging.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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Hotmart looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Response Targets
Hotmart will make a best effort to meet the following response targets for hackers participating in our program. If any additional information is required from you, please allow for another 5 days for our team to review and respond. Our security team often needs to validate internally with our development team. In those cases, your patience will be much appreciated.
| Type of Response | SLA in business days |
|---|---|
| First Response | 5 days |
| Time to Triage | 8 days |
| Time to Resolution | depends on severity and complexity |
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
- Disclosure is strictly prohibited
Program Rules
- ==The *.buildstaging.com environment is available only from .Monday to Friday. Do not perform tests in a production environment.==
- Only test against assets that are explicitly defined in the scope.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible.
- Please, use markdown to send commands and HTTP request/response examples.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only accept the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be accepted the first one.
- 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.
- Although Hackerone has Detailed Platform Standards, the final severity of the vulnerability will be determined by the Hotmart team, considering internal criteria that may result in a different severity.
Subdomain Takeover
Researchers must provide a proof of concept (PoC) demonstrating that the takeover was performed by them (e.g., by creating a PoC that includes their nickname). Takeovers conducted by third parties will be accepted as Informative.
Cross Site Scripting (XSS)
If you found a XSS, please inform in your report:
-
Who is the attacker and the victim of the XSS context? Ex.: Does a customer without privileges affect an admin user through this XSS vulnerability?
-
Does the attacker is able to obtain the victim's session cookie through this XSS vulnerability? If this is not possible, considering the application context, what is the worst thing an attacker could do through this vulnerability?
-
Does the attacker need to encode the XSS payload to bypass some sanitization controls?
Session Layer: HTTP Headers
Researchers should add headers to requests such as:
| Identifier | Format | Example |
|---|---|---|
| Your Username | X-Bug-Bounty: HackerOne- | X-Bug-Bounty: HackerOne-bughunter |
##Big Reward Researchers who demonstrate excellence by submitting 2 valid critical severity reports or 4 valid high severity reports may apply for entry into our prestigious Hotmart private program.
As a member of the Hotmart private program, you’ll unlock:
- Access to various platform features.
- Opportunity to participate in special bug bounty campaigns.
- Higher bounty payouts and more!
About Us
Hotmart is a platform for the distribution of digital products, offering services to host a product, help boosting sales and payment processing. Hotmart has three different profiles that can be found within the platform: Producers, Affiliates and customers.
- Producers are people or companies who publish some kind of digital content to be sold online. This includes courses, e-books or any other form of digital product.
- Collaborators were profiles with permissions to perform certain tasks for the Producers, and help manage their sales and customers. For each collaborator profile, Producers can define specific permissions and add collaborators to each of them.
- Affiliates are people or companies who participate in an Affiliate Program and wish to earn commissions to recommend or promote other people’s or companies’ products.
- Customers are the consumers who buy or access digital products through Hotmart’s platform.
If you want to know more about Hotmart, Producers, Collaborators, Affiliates and Products, please refer to:
Test Plan
-
STOP testing if you are unsure about the impact it may have on our systems. If you think you may cause, or have caused, damage while testing a vulnerability, report your initial finding(s) and request authorization to continue testing.
-
Please use your hacker email alias when testing ([email protected])
-
Only interact with accounts you own or with the explicit permission of the account holder.
-
Include a custom HTTP header in all your traffic. Burp and other proxies allow the easy automatic addition of headers to all outbound requests.
-
Do not upload shells or create a backdoor of any kind.
-
No Data deletion / alter is allowed
-
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.
-
Register an account here: https://sso.buildstaging.com/signup
-
Test Card Information 1
- Card Banner: VISA
- Card number: 4111 1111 1111 1111
- Name on Card: Any name
- Expiration: 03/30
- CVV: 737
-
Test Card Information 2
- Card Banner: MASTERCARD
- Card number: 5555 4444 3333 1111
- Name on Card: Any name
- Expiration: 03/30
- CVV: 737
Processes in the Platform
Registering
- How do I register at Hotmart?
- How can I update my Personal Information?
- How can I update my buyer account to Affiliate/Producer?
- How do I change the e-mail registered in my Hotmart account?
- How can I reset my Hotmart access password?
- General Articles on registering a product
Editing and setting up a product
Frequent questions asked by Producers
- What payment types and methods can I opt for my product?
- What is a subscription product and how to create one?
- General Articles on Managing a product
Creating an offer and discount coupons
- How do I create an offer for my product?
- How do I create an offer for my subscription product?
- How to create discount coupons for my product?
Affiliate Program For producers:
- How do I set up my Affiliate Program?
- How to recruit Affiliates to my product?
- How to manage affiliation requests
General Articles on Affiliate program For affiliates
- How do I become an Affiliate to a product on Hotmart?
- FAQ about Affiliation
- What are HotLinks?
- How to search for products on Hotmart Market?
- What are Hotmart’s rules to attribute commissions?
- General Articles on Commission Tracking
Co-Production
Withdrawals and Extracts
- How to withdraw sales commissions?
- Which status can a withdrawal request take?
- What can stop me from receiving a commission after a sale?
Generating a Brazillian CPF (document ID) If you see some CPF field to fill, you can use a fake CPF generated by a CPF generator, such as:
This fake CPF is just for tests propose
Out of scope vulnerabilities
- Any activity that could lead to the disruption of our service (DoS or DDoS).
- Clickjacking
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Self-exploitation (self XSS, self denial-of-service, etc.), unless a method to attack a different user can be demonstrated.
- 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.
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or other 'load testing' types of issues
- Brute force of promo code
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC/TXT records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
- Internal IP exposure, unless you can do something impressive with it
- Leaking information via the Referer header
- Password or account recovery policies, such as reset link expiration or password complexity
- Account/email Enumeration
- Fixed Session
- Issues related to credentials/info disclosure in public sources such as Trello, GitHub, Wayback, etc, will be analyzed in each case and may not be eligible for bounty.
- Content spoofing, XSS or HTML injection in places where intentionally accepting HTML or via Third-party Subdomain.
- Any GraphQL vulnerabilities with DoS impact
- 0-day and other CVE vulnerabilities reported 30 days after initial publication (CVE List Status of Published).
Nginx Misconfiguration Issues
The following Nginx-related security issues are considered out of scope for this bug bounty program:
-
Common Nginx Configuration Issues:
- Missing security headers (X-Frame-Options, X-Content-Type-Options, etc.)
-
Nginx Proxy Configuration:
- Proxy bypass attempts through header manipulation
- X-Forwarded-For spoofing
-
Server Block Configuration:
- Default error pages exposed
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 Hotmart and our users safe!