- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 4
- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- 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.
- Pays cash
-
No
FreshBooks does not reward for security issues
- Safe harbor
-
Partial
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services
- Hall of fame
-
Yes
FreshBooks thanks the following Internet Security Superstars for their vigilance keeping the online world a safer place:
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 2 excluded.
Web 2
- https://my.freshbooks.com
- https://www.freshbooks.com
APIs 1
- https://api.freshbooks.com
Domains 1
- freshbooks.com
Out of scope (2)
- FreshBooks offices, employees, equipment, etc.
- third-party providers and services
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Freshbooks's policy. "We" in these lines means the program, not this site.
While testing
-
Provide details of the vulnerability, including information needed to reproduce and validate the vulnerability and a Proof of Concept (POC)
-
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 FreshBooks a reasonable time to correct the issue before making any information public
-
When experimenting, please only attack test accounts you control.
-
Do not run automated scans without checking with us first.
-
Do not test the physical security of FreshBooks offices, employees, equipment, etc.
-
Do not test using social engineering techniques (phishing, spear-phishing, pretexting, etc.)
-
Do not perform DoS or DDoS attacks.
-
Do not, in any way, attack our end users or engage in the trade of stolen user credentials.
Not accepted
-
Vulnerabilities in third-party systems will be assessed case-by-case, and most likely will not be eligible for a reward.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.