- 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.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
We do not offer money or swag as rewards, but we will give you a place in our Security Hall of Fame
- Safe harbor
-
Full
Authorized in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls.
- Hall of fame
-
Yes
We do not offer money or swag as rewards, but we will give you a place in our Security Hall of Fame
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.
Self-hosted does not list the scope of this program publicly. Check its policy.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from TV 2 Norway's policy. "We" in these lines means the program, not this site.
While testing
-
Play by the rules. This includes following this policy and any other relevant agreements.
-
Report any vulnerability you have discovered promptly.
-
Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience.
-
Use only the official channels to discuss vulnerability information with us.
-
Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy.
-
Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
-
You should only interact with test accounts you own or with explicit permission from the account holder.
-
Do not engage in extortion.
Not accepted
-
Clickjacking on pages with no sensitive actions.
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions, e.g.: login,logout or search.
-
Attacks requiring MITM or physical access to a user’s device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
-
Rate limiting or bruteforce issues on non-authentication endpoints.
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies that are not sensitive (e.g. missing flags on authentication cookies are in scope).
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version].
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Tabnabbing.
-
Open redirects are out of scope unless an additional security impact can be clearly demonstrated.
-
Issues that require unlikely user interaction.
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.