Најава Започнете сега
Безбедност · Responsible Disclosure

SITE123 Bug Bounty Program

Working with skilled security researchers is crucial to keeping our software and users safe. Our Bug Bounty Program rewards researchers who help us find and fix security vulnerabilities in our systems.

Up to $1,500Maximum reward
3 деновиInitial response
7 деновиTriage completion
30 деновиPayment after confirmation
Опсег

What you can test

Only the assets listed as in scope are eligible for rewards. Anything not listed is out of scope.

In Scope Eligible
  • Web Applications: All customer-facing web applications and dashboards
  • Mobile Applications: iOS and Android mobile apps (latest versions)
  • APIs: All public and authenticated API endpoints
  • Authentication Systems: Login, registration and password reset
  • Data Processing: File upload and processing systems
  • Third-party Integrations: Connected services and plugins
Out of Scope Not eligible
  • Everything that is not listed as in scope
  • Physical Security: Office buildings and data centers
  • Social Engineering: Attacks against employees or customers
  • Denial of Service (DoS): Volume-based attacks or resource exhaustion
  • Spam or Content Issues: Content problems that are not related to security
  • Third-party Services: Issues in external services we don't control
  • Self-XSS: A user pasting code into the browser console
  • Missing Security Headers: With no security impact that can be shown
Vulnerability Categories & Rewards

Rewards by severity

Final reward amounts are based on severity, impact, how easy it is to exploit, the number of affected users and the quality of the report.

Critical up to $1,500

Remote code execution, SQL injection with data access, authentication bypass affecting multiple users, privilege escalation and direct access to sensitive data.

  • Remote Code Execution (RCE) – The ability to run any command on our servers through input validation flaws
  • SQL injection with data access – Database queries that allow extracting user passwords, payment information or personal data
  • Authentication bypass affecting multiple users – Flaws that allow logging in as any user without credentials (for example, token manipulation or session fixation)
Високо up to $1,000

Significant XSS, SSRF with internal access, directory traversal, major authorization flaws and payment system vulnerabilities.

  • Stored Cross-Site Scripting (XSS) in user profiles – Malicious scripts that run when other users view a profile, and may steal session tokens
  • Server-Side Request Forgery (SSRF) with internal access – The ability to send requests to internal services, which may expose admin panels or internal APIs
  • Payment system vulnerabilities – Flaws that allow changing prices, skipping payment or processing transactions without permission
Средно up to $500

CSRF with meaningful impact, sensitive information disclosure, business logic flaws and stored XSS.

  • Cross-Site Request Forgery (CSRF) on sensitive actions – Making users change their password, delete their account or change settings without knowing it
  • Sensitive information disclosure – Exposing user email addresses, phone numbers or private website content through API endpoints
  • Business logic flaws – Getting around premium feature limits, abusing the referral system, or skipping steps in a way that affects revenue
Ниско up to $250

Minor XSS, non-sensitive information disclosure, small misconfigurations and clickjacking with impact.

  • Reflected Cross-Site Scripting (XSS) – Scripts that run only when users click a malicious link, with a limited ability to steal data
  • Information disclosure of non-sensitive data – Revealing user IDs, creation times or public profile details that were not meant to be shown
  • Clickjacking with demonstrated impact – Attacks that trick users into actions they didn't mean to take (you must show a realistic attack)
Informational up to $50

Best practice violations, weaknesses that can't be exploited, and guidance or documentation issues.

  • Missing security headers – No Content Security Policy (CSP), X-Frame-Options or other protective headers (you must show the possible impact)
  • Weak password policy enforcement – Allowing very simple passwords, or no account lockout
  • Information leakage in error messages – Revealing software versions, file paths or the database structure in detailed error messages

* Reward ranges are guidelines only. Final amounts may be higher or lower at our sole discretion.

How to Submit

Submission guidelines

Submit each unique finding as a separate report.

Е-пошта
security@site123.com
Subject line
Bug Bounty – [Vulnerability Type] – [Severity]
Your report should include
Detailed description Affected systems Reproduction steps Impact assessment Supporting evidence Suggested fix
Report Quality Standards
  • Written in English
  • Clear steps that we can reproduce
  • Evidence such as screenshots, code or a video
  • A professional and constructive tone
Правила

Rules of engagement

Please test responsibly. Breaking these rules may disqualify you from the program.

Rules of Engagement
  • Do not exploit a vulnerability beyond what is needed for a proof of concept.
  • Do not access, change or delete data that is not your own.
  • Do not disrupt our services, send spam or attack availability.
  • Give us a reasonable time (usually 90 days) to investigate and fix the issue.
  • Test only with your own accounts whenever possible.
Disqualification Criteria
  • Duplicate reports
  • Out of scope issues
  • Reports without enough details to reproduce the issue
  • Automated scanner output with no manual validation
Process & Payment

Response and rewards process

Here is what happens after you submit a report.

Initial Response

We confirm we got your report within 3 business days.

Triage

We validate the report and set its severity within 7 business days.

Резолуција

We fix the issue according to the severity timelines below.

Плаќање

We pay within 30 денови of confirmation, by PayPal or bank transfer, after we receive a valid invoice.

Critical 30 денови
Високо 60 денови
Medium / Low 90 денови
ЧПП

Frequently asked questions

Can I test in production?

Yes, but you must not affect real users. Use test accounts whenever possible.

What if I access customer data by accident?

Stop right away, report it to us and delete the data. Acting responsibly won't disqualify you.

Do you accept mobile vulnerabilities?

Yes, the latest iOS and Android apps are in scope.

How are rewards decided?

Based on severity, impact, how easy it is to exploit, the number of affected users and the quality of the report.

Can I send several vulnerabilities in one report?

No, please submit each unique finding separately.

What happens if two people report the same bug?

The first valid report we receive is eligible for a reward.

Will you always pay the listed reward amounts?

No. The reward ranges are guidelines only. Final amounts may be higher or lower at our sole discretion.

Can I share the vulnerability publicly after I report it?

No. All vulnerabilities you find must be kept confidential.