Mailtrack
By MAILSUITE S.L. Vulnerability disclosure program on Self-hosted mailtrack.io
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 0
- 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.
- 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
Do not request compensation for security vulnerability reports either from Mailsuite or external vulnerability marketplaces.
- Safe harbor
-
Full
To encourage responsible disclosure, Mailsuite will not bring a lawsuit against you or ask law enforcement to investigate you if we determine that a disclosure meets the following guidelines.
- Hall of fame
-
Yes
Participating Security Researchers
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
0 assets you may test, 11 excluded.
Self-hosted does not list the scope of this program publicly. Check its policy.
Out of scope (11)
- Brute forcing
- Clickjacking on pages without authentication and/or sensitive state changes
- Denial of Service (DoS)
- HTTPOnly flag not set on non-sensitive cookies
- HTTP TRACE method enabled
- Issues only present in old browsers/old plugins
- Logout Cross Site Request Forgery (CSRF)
- Secure flag not set on non-sensitive cookies
- SSL vulnerabilities related to configuration or version
- User enumeration
- Vulnerability reports related to the reported version numbers of web servers, services, or frameworks
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Mailtrack's policy. "We" in these lines means the program, not this site.
While testing
-
Please provide us a reasonable time period to address the issue before public disclosure.
-
Make a reasonable effort to avoid service disruption (e.g. DoS), privacy issues (i.e. accessing a Mailsuite user’s data), and data destruction when performing vulnerability research.
-
Do not request compensation for security vulnerability reports either from Mailsuite or external vulnerability marketplaces.
-
Do not phish or social engineer employees, partners, or users of Mailsuite.
-
Do not run automated scanning tools and send us the output without confirming the issue is present.
Not accepted
-
SSL vulnerabilities related to configuration or version
-
Denial of Service (DoS)
-
User enumeration
-
Brute forcing
-
Secure flag not set on non-sensitive cookies
-
HTTPOnly flag not set on non-sensitive cookies
-
Logout Cross Site Request Forgery (CSRF)
-
Issues only present in old browsers/old plugins
-
HTTP TRACE method enabled
-
Vulnerability reports related to the reported version numbers of web servers, services, or frameworks
-
Clickjacking on pages without authentication and/or sensitive state changes
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.