Cronometer
Bug bounty on security.txt cronometer.com
- Top reward
- Not published
- 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.
- Pays cash
- Amounts are not published; ask before you invest time.
- 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.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
In some circumstances, and at Cronometer’s sole discretion, Cronometer may decide to provide a reward to independent security researchers
- Response
-
Within 3 days
We will make every effort to respond to security reports within a few days, but please be patient.
- Safe harbor
-
Full
As long as you follow these terms, we will consider your research activity authorized and will not initiate legal action against you regarding that research activity under applicable anti-hacking laws.
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, 8 excluded.
Android apps 1
- Android apps
Domains 1
- cronometer.com
Products and areas 1
- Cronometer web-based service
Out of scope (8)
- Clickjacking with no practical security impact
- DDOS of blog/wordpress
- Email spoofing / SPF/DKIM/DMARC policies
- Login and logout CSRF.
- Missing HTTP security headers
- Password Policies
- Rate limiting
- User enumeration
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Cronometer's policy. "We" in these lines means the program, not this site.
While testing
-
You may test security issues against your own user account or unique test accounts that you create, but accessing other users’ accounts or data is strictly prohibited.
-
Your research activity must not harm other users.
-
Never exfiltrate or change data on our systems.
-
If you accidentally encounter user data, please inform us immediately.
-
Do not conduct testing that affects the general availability of Cronometer, such as DDOS.
Not accepted
-
Login and logout CSRF.
-
Rate limiting
-
Email spoofing / SPF/DKIM/DMARC policies
-
User enumeration
-
Password Policies
-
Missing HTTP security headers
-
Clickjacking with no practical security impact
-
DDOS of blog/wordpress
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 12 Nov 2026. Last checked 3 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.