🛡️ Introduction
At MITE3, we strive for a high level of security in our ICT systems. However, vulnerabilities can still occur. We greatly appreciate your help in identifying and reporting them responsibly.
This procedure is based on the Responsible Disclosure guideline from the Dutch National Cyber Security Centre (NCSC).
🕵️♂️ Found a Vulnerability?
Have you discovered a weakness in one of our systems? Please let us know as soon as possible via security@mite3.nl. We’re happy to work with you to resolve the issue safely and quickly.
📋 What We Ask From You
- Email your findings to security@mite3.nl
- Provide sufficient information to reproduce the issue, such as a URL, IP address, and a brief description
- Include a way to contact you (e.g., email address or phone number), so we can coordinate a solution
- Report the vulnerability as soon as possible after discovery
- Do not share your findings with others until the issue has been resolved
- Act responsibly with the knowledge: demonstrate the issue exists without causing further harm
🚫 What You Are Not Allowed to Do
To enable safe research without legal risks, the following actions are explicitly prohibited:
- Installing malware
- Copying, modifying, or deleting data
- Making changes to systems
- Accessing systems repeatedly or sharing access with others
- Brute-forcing access (using automated login attempts)
- Conducting Denial-of-Service attacks
- Using social engineering techniques (such as phishing or deceiving employees)
✅ What You Can Expect From Us
If you adhere to the above conditions:
- No legal consequences will be associated with your report
- You will receive an acknowledgment within 3 business days
- You will receive a substantive response within 5 business days, including an assessment and expected resolution timeframe
- We will keep you informed of the progress
- We will resolve the issue as soon as possible, no later than 90 days
- With your consent, you may be credited as the discoverer, for example in our Hacker Hall-of-Fame
- Your report will be treated confidentially and your personal data will not be shared with third parties (unless legally required)
🎁 Reward
Depending on the severity of the security issue and the quality of your report, we may offer an appropriate reward. This could range from a T-shirt to a maximum of €100.
Conditions:
- The vulnerability must be new and significant
- The vulnerability must not relate to up-to-date, off-the-shelf software or cloud services we use
- You must enable us to verify the issue
📨 Submit a Report
Send your report to security@mite3.nl. Please include the following if possible:
Contact information:
- Name or nickname
- Email address
Technical details:
- IP address(es)
- Domain name / URL
- Relevant headers or payloads (if applicable)
Description of the vulnerability:
- Explanation of the issue
- Risk or potential impact
- Any proof-of-concept
- Suggestions for a fix
📄 For more information, see our security.txt file:
https://mite3.nl/.well-known/security.txt
🏅 Hacker Hall-of-Fame
We are grateful to the security researchers who contribute to our digital safety. Below is an overview of valid vulnerability reporters who have been included in our Hall-of-Fame with their permission.
Have you discovered a vulnerability? Please follow the reporting procedure above – we’d be happy to recognize your contribution.
Date | Researcher | Description |
---|---|---|
2023/12/10 | Raju Basak | Security misconfiguration in HTTP response headers: unsafe-inline and unsafe-eval present in the Content-Security-Policy. No patch available from WordPress or third-party plugins; compensating controls implemented. |
2021/01/29 | Chan Nyein Wai | Denial of Service (DoS) vulnerability in load-styles.php . No patch available from WordPress; mitigated using compensating controls following the related 2019/06/03 CVE-2018-6389 report. |
2020/09/08 | Shebi Levi | Denial of Service (DoS) vulnerability in wp-cron.php . No patch available from WordPress; mitigated through compensating measures. |
2020/04/02 | Gul Hamee | Tabnabbing vulnerability affecting external links. Resolved by removing target="_blank" attributes or adding appropriate rel attributes to prevent exploitation. |
2019/08/06 | Mansouri Badis | Denial of Service (DoS) vulnerability in the XML-RPC interface. No official patch provided by WordPress; mitigated using compensating controls. |
2019/06/03 | Asim | Denial of Service (DoS) vulnerability in load-scripts.php (CVE-2018-6389). No official fix released; compensating controls applied. |