Skip to content

Zooz

Bug bounty on Self-hosted zooz.com

Accepting reports
Top reward
Not published
Top severity paid
Not published
Assets in scope
6
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report as the policy says
The policy page explains how.
No public write-ups
Keep findings private.

Rewards

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

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes To show our appreciation for security researchers, we operate a bug bounty (reward) program for those who have responsibly disclosed vulnerabilities to us.

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

Scope

6 assets you may test, 5 excluded.

Domains 5

  • admin.zooz.com
  • control.paymentsos.com
  • developers.paymentsos.com
  • paymentsos.com
  • zooz.com

APIs 1

  • api.paymentsos.com
Out of scope (5)
  • Any direct API call from paymentsos.com / zooz.com to zendesk.com i.e. support tile in control center
  • Direct testing of 3rd parties (for example, testing Zendesk directly for any reason)
  • DMARC records
  • Email invitation feature
  • Zooz repos on Github / Gitlab

Rules

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

While testing

  • Do not disclose vulnerabilities to others.
  • Do not exploit vulnerabilities any further than necessary than to prove their existence.
  • Do not access, alter or download data belonging to legitimate users of the site.
  • Do not perform any activity that could lead to the disruption of our service (DoS/DDoS).
  • Do not test in a manner that would result in the sending of unsolicited or unauthorized junk mail or unsolicited messages
  • Do not test third-party applications or services that are integrated with PaymentsOS.
  • Do not perform social engineering attacks.
  • Not violate any laws.
  • Create an account with an email that contains the word ‘bounty’ .
  • Testing is only authorized on the targets listed as In-Scope.

Not accepted

  • Both paymentsos.com and zooz.com have missing DKIM/DMARC (No Spoofing Protection on Email Domain)
  • control.paymentsos.com doesn’t invalidate existing session upon password reset
  • HSTS header is missing from all domains
  • No Rate Limiting (Global) on APIs and resources
  • Domain take over using webflow.com

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 6 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.