Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Clipperz

Vulnerability disclosure program on Self-hosted clipperz.is

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
3
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 3 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

This program does not pay cash rewards.

Response
Within 3 days work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission);
Safe harbor
Full not pursue or support any legal action related to your research;
Hall of fame
Yes publicly recognize your contribution (website, twitter, …), if you are the first to report the issue and we make a code or configuration change based on the issue.

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, 5 excluded.

Web 1

  • https://clipperz.is

Products and areas 2

  • company website
  • web app: online vault and password manager
Out of scope (5)
  • findings derived primarily from social engineering (e.g. phishing, vishing);
  • findings from applications or systems not listed in the ‘Scope’ section;
  • findings from physical testing such as office access (e.g. open doors, tailgating);
  • network level Denial of Service (DoS/DDoS) vulnerabilities.
  • UI and UX bugs and spelling mistakes;

Rules

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

While testing

  • make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
  • perform research only within the scope set out below;
  • use the identified communication channels to report vulnerability information to us;
  • keep information about any vulnerabilities you’ve discovered confidential between yourself and Clipperz until we’ve had 30 days to resolve the issue.

Not accepted

  • Personally identifiable information (PII)
  • UI and UX bugs and spelling mistakes
  • network level Denial of Service (DoS/DDoS) vulnerabilities
  • findings derived primarily from social engineering (e.g. phishing, vishing)
  • findings from physical testing such as office access (e.g. open doors, tailgating)

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.