hostinger

#HOSTINGER BUG BOUNTY REWARD PROGRAM

PLEASE READ THIS AGREEMENT CAREFULLY, AS IT CONTAINS IMPORTANT INFORMATION REGARDING YOUR LEGAL RIGHTS AND REMEDIES. Last Revised: 2026-10-21

#RESPONSIBLE DISCLOSURE POLICY Hostinger encourages the responsible disclosure of security vulnerabilities in our services or on our website. In order to facilitate the responsible disclosure of security vulnerabilities, we agree that if, in our sole discretion, we conclude that a disclosure meets all of the guidelines of the Hostinger Bug Bounty Reward Program, Hostinger will not bring any private or criminal legal action against the disclosing party.

#BUG BOUNTY REWARD PROGRAM POLICY AND TERMS Our team of dedicated security professionals works vigilantly to help keep customer information secure. We recognize the important role that security researchers and our user community play in helping to keep Hostinger and our customers secure. If you discover a site’s or product’s vulnerability, please notify us using the guidelines below.

#PROGRAM TERMS Please note that your participation in the Bug Bounty Reward Program (“Bug Bounty Program”) is voluntary and subject to the terms and conditions set forth on this page (“Program Terms”). By submitting a site or product vulnerability to Hostinger, you acknowledge that you have read and agreed to these Program Terms. These Program Terms supplement the Terms of Service and Privacy Policy and any other agreement you have entered with Hostinger. The terms of those Hostinger agreements will apply to your use of and participation in the Bug Bounty Program as if fully set forth herein. If any inconsistency exists between the Terms of Service, Privacy Policy and these Program Terms, these Program Terms will prevail, but only with regard to the Bug Bounty Program. To encourage responsible disclosures, Hostinger commits that if we conclude, in our sole discretion, that a disclosure respects and meets all the guidelines of these Program Terms, Privacy Policy and Terms of Service, Hostinger will not bring a private action against you or refer a matter for public inquiry. As part of your research, you shall not modify any files or data, including permissions, and shall not intentionally view or access any data beyond what is needed to prove the vulnerability.

Hostinger will make its best effort to adhere to the following response targets: Type of Response - Business days First Response - 2 working days Time to Triage - 5 working days Time to Bounty - 14 working days Time to Resolution - depends on severity and complexity

#TESTING CREDENTIALS

To prevent abuse of shared credentials, we do not provide access to shared testing accounts. Instead, Bug Bounty Program participants must register a new account at hostinger.com. Participants can receive a coupon covering one month of our Premium Shared Hosting plan. To claim your coupon, please contact our Security team at [email protected] and include the following details in your message:

• Your HackerOne username
• The email address used to register your Hostinger account
• A short notice that you are participating in a Bug Bounty Program through HackerOne

Once verified, our team will provide you with a coupon code that covers all expenses for one month of Premium Shared Hosting.

#BEFORE YOU SUBMIT - PLEASE READ

To keep the program focused, the following are closed as Not Applicable, usually without further review. Please check your report against this list first:

• No working proof-of-concept demonstrating real impact on an in-scope asset.
• No reasonable attack scenario (requires unrealistic preconditions, significant/unlikely user interaction, or prior account compromise).
• Target not in the in-scope domain list above.
• Phishing, scam, or spam content on a customer site - report it to [email protected], not here.
• Only affects your own account, hosting, VPS, or sandbox (only cross-tenant issues or impact on internal systems qualify).

*Note: we only reward vulnerabilities caused by our systems. Issues related to the cPanel platform itself are not eligible for rewards.

New Hosting plan - Agency

We have new launched Agency hosting plans that are built entirely on our H5G infrastructure, which is designed specifically for WordPress hosting. These plans provide complete site isolation to boost security and performance. They also facilitate access sharing for each site, supporting smooth collaboration among team members.

Since the Agency plan is fully powered by H5G, its security testing scope (including Bounty Payments) falls under our existing H5G Infrastructure scope. We invite researchers to help identify potential vulnerabilities.

To participate in testing our new hosting plans, please email [email protected] and ask for a coupon for the Agency plan testing. Include the email address you used to register for Hpanel in your email.

#ELIGIBILITY REQUIREMENTS To be eligible for the Bug Bounty Program, you must not:

• Be in violation of any national, state, or local law or regulation;
• Be employed by Hostinger or its subsidiaries;
• Be an immediate family member of a person employed by Hostinger or its subsidiaries or affiliates; or
• Be less than 16 years of age. If you are at least 16 years old but are considered a minor in your place of residence, you must get your parents’ or legal guardian’s permission prior to participating in the program.
• If Hostinger discovers that you meet any of the criteria above, Hostinger will remove you from the Bug Bounty Program and disqualify you from receiving any Bounty Payments.

#DISCLOSURE GUIDELINES By providing a submission through HackerOne or agreeing to the Program Terms, you agree that you shall not publicly disclose your findings or the contents of your Submission to any third parties in any way without Hostinger's prior written approval. Failure to comply with the Program Terms will result in immediate disqualification from the Bug Bounty Program and ineligibility for receiving any Bounty Payments.

#QUALIFYING VULNERABILITIES: Hostinger will accept a report of any vulnerability that substantially affects the confidentiality or integrity of any eligible Hostinger service. Eligible vulnerabilities include, but are not limited to:

• Authentication or authorization flaws, including insecure direct object references and authentication bypass
• Server-side or remote code execution (RCE)
• Injection vulnerabilities, including SQL and XML injection
• Directory Traversal
• Privilege Escalation
• Disclosure of sensitive or personally identifiable information
• Significant security misconfiguration with a verifiable vulnerability
• Exposed system credentials, disclosed by Hostinger or its employees, that pose a valid risk to an in-scope asset

#NON-QUALIFYING VULNERABILITIES: Any domain not listed in the policy scope is out of scope for the purposes of the Bug Bounty Program, as is all hosted customer content and third-party programs and plug-ins. The following actions do not qualify for the Bug Bounty Program and should not be tested by researchers participating in the Bug Bounty Program:

• Reports that involve a secondary user account where an existing business relationship is being leveraged and the impact is limited solely to the parent account
• Username enumeration on customer-facing systems (i.e., using server responses to determine whether a given account exists)
• Scanner output or scanner-generated reports, including any automated or active exploit tool
• Man-in-the-Middle attacks
• Any physical attacks against Hostinger's property or data centers
• Self Cross-Site Scripting (XSS)
• Cross-Site Request Forgery (CSRF)
• Click-jacking
• Vulnerabilities involving stolen credentials or physical access to a device
• Phishing attacks
• Social engineering attacks, including those targeting or impersonating internal employees by any means (e.g., customer service chat features, social media, personal domains, etc.)
• Open redirection, except in the following circumstances:
  • Clicking a Hostinger-owned URL immediately results in an unexpected redirection and loss of sensitive data (e.g., session tokens, PII, etc). Open OAuth client registration is public by design, therefore issue related to it will be treated as N/A.
• CRIME/BEAST attacks
• Logout CSRF
• Banner or version disclosures
• Missing or misconfigured SPF records
• Directory listing (unless sensitive data can be found)
• DoS, brute force, user enumeration, or DDoS attacks
• Blackhat SEO techniques
• Any other submission determined to be low risk, based on unlikely or theoretical attack vectors, requiring significant user interaction, or resulting in minimal impact
• Vulnerabilities on third-party libraries without showing specific impact on the target application (e.g., a CVE with no exploit)
• Exposed credentials that are either no longer valid or do not pose a risk to an in-scope asset
• Any bug that relies upon an outdated browser
• Infrastructure vulnerabilities, including:
  • Issues related to SSL certificates
  • DNS configuration issues
  • Server configuration issues (e.g., open ports, TLS versions, etc.)
• Bugs requiring exceedingly unlikely user interaction.
• Password complexity requirements
• Email verification/validation issues
• Quality and business logic bugs that do not pose a real risk and do not impact business and customers in a way that could lead to unauthorized access to data or systems, also when there is no possibility to take advantage of the bug to cause some sort of damage to company systems or data.
• Vulnerabilities on individual clients' infrastructure or virtual private servers (VPS), including websites, databases, etc.
• Hacking discount coupons
• Broken links
• Reports without a working proof-of-concept, or based only on HTTP headers, banners, versions, or configuration observations
• Missing or misconfigured security headers (CSP, X-Frame-Options, HSTS, etc.) without a demonstrated exploit
• Phishing, scam, malware, or spam content hosted on customer sites (report to [email protected], not through this program)
• CORS misconfiguration without a demonstrated cross-origin theft of sensitive data (a reflected Origin or Access-Control-Allow-Origin header alone is not sufficient)
• SSRF where only an HTTP/DNS interaction is shown (must reach internal resources or retrieve internal/sensitive data)
• Access to your own AI/Horizons/preview sandbox's files, source code, or environment variables (only cross-tenant access qualifies)
• Executing commands, uploading files, or reading system files (e.g. /etc/passwd) on your own hosting account or VPS, or IDOR/BOLA on your own objects (only cross-tenant access qualifies)
• Race conditions whose only effect is obtaining a single paid feature, extra trial credits/quota, or a duplicate-named resource, with no cross-tenant access, privilege escalation, or data exposure
• API tokens working independently of interactive 2FA, sessions remaining valid after a password change, or password-reset tokens valid within their expiry window (by design)
• Public-by-design client-side keys embedded in the browser (analytics, error-tracking, real-time messaging, OAuth client IDs)
• Rate-limit bypass via IP rotation, proxies, or distributed requests, and OTP/2FA brute force
• Vulnerabilities requiring localhost or a process running on the victim's own machine (e.g. previewApp loaders)

#BUG SUBMISSIONS REQUIREMENTS Required information For all submissions, please include:

• Full description of the vulnerability being reported, including the exploitability and impact
• Evidence and explanation of all steps required to reproduce the submission, which may include:
• Videos or step-by-step screenshots
• Exploit code
• Traffic logs
• Web/API requests and responses
• Email address or user ID of any test accounts
• IP address used during testing
• For RCE submissions, see below Failure to include any of the above items may delay or jeopardize the Bounty Payment

#REMOTE CODE EXECUTION (RCE) SUBMISSIONS GUIDELINES: Failure to meet the below conditions and requirements could result in a forfeiture of any potential Bounty Payment.

• Source IP address

• Timestamp, including time zone

• Full server requests and responses

• Filenames of any uploaded files, which must include “bugbounty” and the timestamp

• Callback IP and port, if applicable

• Any data that was accessed, either deliberately or inadvertently

• Allowed Actions:

  • Directly injecting benign commands via the web application or interface (e.g., whoami, hostname, ifconfig)
  • Uploading a file that outputs the result of a hard-coded benign command

• Prohibited Actions:

  • Uploading files that allow arbitrary commands (i.e., a webshell)
  • Modifying any files or data, including permissions
  • Deleting any files or data
  • Interrupting normal operations (e.g., triggering a reboot)
  • Creating and maintaining a persistent connection to the server
  • Intentionally viewing any files or data beyond what is needed to prove the vulnerability
  • Failing to disclose any actions taken or applicable required information

#BOUNTY PAYMENTS You may be eligible to receive a monetary reward (“Bounty Payment”) if: (i) you are the first person to submit a site or product vulnerability; (ii) that vulnerability is determined to be a valid security issue by Hostinger's security team at their sole discretion; and (iii) you have complied with all Program Terms. Bounty Payments, if any, will be determined by Hostinger in Hostinger's sole discretion. In no event shall Hostinger be obligated to pay you a bounty for any Submission. All Bounty Payments shall be considered gratuitous. All Bounty Payments will be made in United States dollars (USD). You will be responsible for any tax implications related to Bounty Payments you receive, as determined by the laws of your jurisdiction of residence or citizenship. Hostinger will determine all Bounty Payments based on the risk and impact of the vulnerability. The minimum bounty amount for a validated bug submission is $100 USD, and the maximum bounty for a validated bug submission is $25000 USD. Hostinger security team retains the right to determine if the bug submitted to the Bug Bounty Program is eligible. All determinations as to the amount of a bounty made by the Hostinger Bug Bounty Team are final. Bounty Payment ranges are based on the classification and sensitivity of the data impacted, ease of exploit, and overall risk to Hostinger customers and the Hostinger brand and determined to be a valid security issue by Hostinger's security team.

#RETESTING

Please note that we reserve the right to request or decline retesting of reported issues at our discretion, based on our internal assessment and priorities. Our decision will take into account factors such as the severity of the issue, the quality of the initial report, and our current resource availability.

To recognize the additional effort involved in retesting, we offer retest bounties as follows:

• Low and Medium Severity Issues: $50 USD
• High and Critical-Severity Issues: $100 USD

#OWNERSHIP OF SUBMISSIONS As a condition of participation in the Bug Bounty Program, you hereby grant Hostinger, its and affiliates a perpetual, irrevocable, worldwide, royalty-free, transferrable, sublicensable (through multiple tiers) and non-exclusive license to use, reproduce, adapt, modify, publish, distribute, publicly perform, create derivative work from, make, use, sell, offer for sale and import the Submission, as well as any materials submitted to Hostinger in connection therewith, for any purpose. You should not send us any Submission that you do not wish to license to us. You hereby represent and warrant that the Submission is original to you, and you own all rights, titles, and interests in and to the Submission. Further, you hereby waive all other claims of any nature, including express contract, implied-in-fact contract, or quasi-contract, arising out of any disclosure of the Submission to Hostinger. In no event shall Hostinger be precluded from discussing, reviewing, developing for itself, having developed, or developing for third parties, materials that are competitive with those set forth in the Submission irrespective of their similarity to the information in the Submission, so long as Hostinger complies with the terms of participation stated herein.

#TERMINATION In the event (i) you breach any of these Program Terms or the Terms of Service of the Hostinger; or (ii) Hostinger determines, in its sole discretion that your continued participation in the Bug Bounty Program could adversely impact Hostinger (including, but not limited to, presenting any threat to Hostinger's systems, security, finances and/or reputation) Hostinger may immediately terminate your participation in the Bug Bounty Program and disqualify you from receiving any Bounty Payments. Please follow these Program Terms.

#CONFIDENTIALITY Any information you receive or collect about Hostinger, Hostinger employees, or any Hostinger customer through the Bug Bounty Program (“Confidential Information”) must be kept confidential and only used in connection with the Bug Bounty Program. You shall not use, disclose, or distribute any such Confidential Information, including, but not limited to, any information regarding your Submission and information you obtain when researching the Hostinger sites, without Hostinger's prior written consent. Any disclosure of Confidential Information outside of this requirement will result in immediate removal from the Bug Bounty Program.

#INDEMNIFICATION In addition to any indemnification obligations you may have under the Terms of Service, you agree to defend, indemnify and hold Hostinger, its affiliates, and the officers, directors, agents, employees, and suppliers of Hostinger, harmless from any claim or demand (including attorneys’ fees) made or incurred by any third party due to or arising out of your Submissions, your breach of these Program Terms and/or your improper use of the Bug Bounty Program.

#CHANGES TO PROGRAM TERMS The Bug Bounty Program, including its policies, is subject to change or cancellation by Hostinger at any time without notice. As such, Hostinger may amend these Program Terms and/or its policies at any time by posting a revised version on our website. By continuing to participate in the Bug Bounty Program after Hostinger posts any such changes, you accept the Program Terms, as modified.