Skip to content

iPaidThat

Bug bounty on Self-hosted ipaidthat.io

Accepting reports Full safe harbor
Top reward
$500
Top severity paid
Critical
Assets in scope
3
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $500
for critical bugs.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

Severity Reward
Critical $500
High $200
Medium $100
Top reward
$500 Critical Remote code execution SQL Injection Data leak Server Access 500$+
Safe harbor
Full we will not take legal action against you nor ask law enforcement to investigate you provided you comply with the following Responsible Disclosure Guidelines:
Hall of fame
Yes On top of this reward, we will also list you here in the Special Thanks session (if you accept)

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test, 3 excluded.

APIs 1

  • API related endpoints on ipaidthat.io

Domains 1

  • ipaidthat.io

Web 1

  • Website related endpoints on https://ipaidthat.io
Out of scope (3)
  • Any domain that is not listed in the Domains section
  • Any other iPaidThat subdomains
  • https://ipaidthat.io/mag

Rules

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

While testing

  • PLEASE DO NOT RUN ANY AUTOMATIC SCAN AGAINST OUR INFRASTRUCTURE.
  • Create an account with the following phone number: +336 13371337
  • Do not create more than 5 accounts.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services.
  • Do not modify or access data that does not belong to you.
  • Give iPaidThat a reasonable time to correct the issue before making any information public, and ask for our approval before making any disclosure.

Not accepted

  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking on pages with no sensitive actions
  • CSV Injection
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • E-mail validation
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours 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.