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

ProductBoard, Inc.

Vulnerability disclosure program on HackerOne productboard.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
2
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 on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test.

Wildcard domains 2

  • *.productboard.com Critical No bounty
  • *.satismeter.com Critical No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from ProductBoard, Inc. (via HackerOne)'s policy.

While testing

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

Not accepted

  • Vulnerabilities without a well-documented attack vector (e.g. only missing best practices)
  • Denial of service or Distributed Denial of service attacks
  • Absence of rate limiting
  • Permission issues in Portals and Legacy boards.
  • HTML and Markdown injection in Productboard Editor and Comments
  • Presence/absence/misconfiguration of SPF/DKIM/DMARC records or any email misconfiguration in general
  • Lack of CSRF tokens
  • Clickjacking issues
  • Missing security headers which do not lead directly to a vulnerability
  • Reports from automated tools or scans
  • Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner)
  • Outdated software without any noteworthy vulnerability
  • Password reset token, account activation or invitation token leaks to third party services
  • EXIF metadata issues
  • Jira Service Desk is open to public
  • Using features from higher plans and other licensing issues

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

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

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

#Brand Promise

ProductBoard looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

#Scope

This policy applies to any digital assets, owned, operated, or maintained by ProductBoard, Inc., including public facing websites.

Please check out especially our recently released features.

#Out of Scope

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Vulnerabilities without a well-documented attack vector (e.g. only missing best practices)
  • Denial of service or Distributed Denial of service attacks
  • Absence of rate limiting
  • Permission issues in Portals and Legacy boards.
  • HTML and Markdown injection in Productboard Editor and Comments
  • Presence/absence/misconfiguration of SPF/DKIM/DMARC records or any email misconfiguration in general
  • Lack of CSRF tokens
  • Clickjacking issues
  • Missing security headers which do not lead directly to a vulnerability
  • Reports from automated tools or scans
  • Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner)
  • Outdated software without any noteworthy vulnerability
  • Password reset token, account activation or invitation token leaks to third party services
  • EXIF metadata issues
  • Jira Service Desk is open to public
  • Using features from higher plans and other licensing issues

#Disclosure Policies

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Follow HackerOne's disclosure guidelines.

#Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep ProductBoard, Inc. and our users safe!