- Top reward
- No cash rewards
- 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.
- 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.
- 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.
This program does not pay cash rewards.
- Pays cash
-
No
Unfortunately, due to ORF’s funding structure, it is not currently possible for us to offer a paid bug bounty program.
- Response
-
Within 3 days
you will receive an acknowledgement e-mail from ORF Security Team, usually within 72 hours of your report being received.
- Safe harbor
-
Full
ORF will not seek prosecution of any security researcher who reports in good faith and in accordance with this policy, any security vulnerability on an in-scope ORF service.
- Hall of fame
-
Yes
We will also offer to include reporters of qualifying vulnerabilities on our acknowledgments page and we'll ask for the details you wish to be included.
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, 11 excluded.
Web 1
- https://orf.at
Out of scope (11)
- Any services hosted by 3rd party providers and services
- Credit card holder data
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- Personally, identifiable information (PII)
- Reports of non-exploitable vulnerabilities and/or reports indicating that our services do not fully align with „best practice“ (e.g. missing security headers)
- TLS configuration weaknesses (e.g. „weak“ ciphersuite support, TLS1.0 support etc.)
- UI and UX bugs and spelling mistakes
- Volumetric vulnerabilities
Rules
What the policy asks of you, and the bug types it won't reward, quoted from ORF's policy. "We" in these lines means the program, not this site.
While testing
-
Access unnecessary amounts of data. For example, 2 or 3 records is enough to demonstrate most vulnerabilities (such as an enumeration or direct object reference vulnerability);
-
Violate the privacy of ORF users, staff, contractors, systems etc. For example, by sharing, redistributing and/or not properly securing data retrieved from our systems or services;
-
Communicate any vulnerabilities or associated details via methods not described in this policy or with anyone other than your dedicated ORF security contact;
-
Modify data in our systems/services which is not your own;
-
Place or insert any kind of malicious code on the system;
-
Disrupt our service(s) and/or systems; or
-
Disclose any vulnerabilities in ORF systems/services to 3rd parties/the public prior to ORF confirming that those vulnerabilities have been mitigated or rectified.
-
ORF requests that all data retrieved during research is securely deleted as soon as it is no longer required and at most, 1 month after the vulnerability is resolved, whichever occurs sooner.
Not accepted
-
UI and UX bugs and spelling mistakes
-
Reports of non-exploitable vulnerabilities and/or reports indicating that our services do not fully align with „best practice“ (e.g. missing security headers)
-
Network level Denial of Service (DoS/DDoS) vulnerabilities
-
TLS configuration weaknesses (e.g. „weak“ ciphersuite support, TLS1.0 support etc.)
-
Volumetric vulnerabilities
-
Personally, identifiable information (PII)
-
Credit card holder data
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.