- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- 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
Depending on the severity of the finding, we are willing to offer a bounty.
- Response
-
Within 3 days
We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date.
- Safe harbor
-
Partial
Nevertheless, if you act in good faith and according to Modat’s rules, we will not report your actions to the authorities, unless we are required to do so by law.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 1 excluded.
Domains 1
- modat.io
Out of scope (1)
- Domains not owned by Modat
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Modat's policy. "We" in these lines means the program, not this site.
While testing
-
Reports are required to be written in English and please include a clear attack scenario outlining detailed reproduction steps.
-
During your investigation make sure that you do not cause any damage or disruptions to our systems so do not alter, change or delete data from our systems.
-
It is not allowed to put a backdoor in the system, not even for the purpose of showing the vulnerability, as inserting a backdoor will cause even more damage to the safety of our systems.
-
Do do not penetrate the system any further than required for the purpose of your investigation.
-
During your research make sure that you do not inadvertently cause a data breach (i.e. sharing screenshots or recordings on 3rd party cloud solution).
-
Do not utilise social engineering to gain access to our systems.
Not accepted
-
Pre-Auth Account takeover/OAuth squatting
-
Self-XSS that can't be used to exploit other users
-
Verbose messages/files/directory listings without disclosing any sensitive information
-
CORS misconfiguration on non-sensitive endpoints
-
Missing cookie flags
-
Missing security headers
-
Cross-site Request Forgery with no or low impact
-
Presence of autocomplete attribute on web forms
-
Reverse tabnabbing
-
Bypassing rate-limits or the non-existence of rate-limits.
-
Best practices violations (password complexity, expiration, re-use, etc.)
-
Clickjacking on pages with no sensitive actions
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, etc.)
-
Mixed content type issues
-
Cross-domain referrer leakage
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Content injection on error pages
-
Username/email enumeration
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homography/typosquatting
-
XMLRPC enabled
-
Banner grabbing/Version disclosure
-
Open ports without an accompanying proof-of-concept demonstrating vulnerability
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.