Vulnerability Disclosure Policy

We take the security of our systems seriously, and we value the security community. We also know that even the most well-designed products are not bug-free. The disclosure of security vulnerabilities helps us ensure the security and privacy of our users.


We require that all researchers

  • Make every effort to avoid privacy violations, degradation of user experience, disruption
  • to production systems, and destruction of data during security testing.
  • Perform research only within the scope set out below.
  • Use the identified communication channels to report vulnerability information to us.
  • Keep information about any vulnerabilities you’ve discovered confidential between yourself and Debricked until we’ve had 90 days to resolve the issue.
  • When you create an account on our service, please use “pentester” as the company name.

If you follow these guidelines when reporting an issue to us, we commit to:

  • Not pursue or support any legal action related to your research.
  • Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission).
  • Recognize your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue and we make a code or configuration change based on the issue.

Non-bounty Issues

We receive many reports on issues that we do not consider to be a risk for us or our customers. Many of which are included in the list here Please read the list carefully before submitting reports to us.

Out of Scope

In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:

  • Findings from physical testing such as office access (e.g. open doors, tailgating)
  • Findings derived primarily from social engineering (e.g. phishing, vishing)
  • Findings from applications or systems not listed in the ‘Scope’ section
  • UI and UX bugs and spelling mistakes
  • Network level Denial of Service (DoS/DDoS) vulnerabilities

Things we do not want to receive:

  • Personally identifiable information (PII)
  • Credit card holder data

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing Please include the following details with your report

  • Description of the location and potential impact of the vulnerability. Here, we regard a vulnerability to be a weakness that can be exploited to violate a security policy in terms of confidentiality, integrity and/or availability.
  • A detailed description of the steps required to reproduce the vulnerability (PoC scripts, screenshots, and compressed screen captures are all helpful to us).
  • Your name/handle and a link for recognition in our Hall of Fame.
  • Monetary rewards may be given for significant vulnerabilities and findings. However, due to the administrative complexities in Sweden for giving out monetary rewards to individuals, payments can be made to registered companies only . Either your own, or a third party such as Upwork.

Note that even though we are happy to receive information about not following best-practices, such issues are not vulnerabilities, unless they affect confidentiality, integrity and/or availability. Similarly, such issues will not result in monetary rewards, though they could award a mention in our Hall of Fame if we find them particularly interesting and useful.

Some best practices and issues of low relevance are already in our backlog. They will be fixed but are not prioritized. For this reason, many reports are duplicates of things that have been reported before. However, all customers can rest assured that all important security issues are immediately responded to and fixed.

Here is an excerpts of issues that we deem not prioritized:

  • Information disclosure in a Wordpress plugin that refers to publicly available information, affecting the following URLs:
  • Questionable categorizations done by our proactive password checker
  • Do not require 2FA when disabling 2FA (only affecting logged in users)
  • No termination of session when adding 2FA

Please respect our decisions and assessments. We are not going to engage in long discussions and arguments regarding best practices and their relevance.

If you’d like to encrypt the information, please use our PGP key.


mQINBGArwQUBEADLZNJ+WuJ1fJsT3dyAGARM/BapiTTM5pZ9TXYg/2kvfQosZ16i erGKln7MAsu3Yo4Z7VkOt4T6yHaAhMZQnlZGi+DtLwNI/YMP6i3JyJJ8GFzqD0rD nEVrAK2QeYxBNkVqtaKaLoMkIdZYc8aGhpvKVVX2TENtmexixyXOnB9MO69xkCvY FVGDraw1tMxjycfWbOrYiSY/wfauzRy+aFDpSgG5ZO57nkFLDscD+ZxKjfCDzoCg 0JxQCa7wAG+xQL8iU/NVX1GGMyyrBZTf25GP7BffpmjSKcst4veQjxqZNAtMt80L N1laotMAiVTddh9dMHA2oFAtGvRoIO7tt3ZZm3i5zT554VhnJeYHCqNvSTyZYlJz QUI0rIGFqfWnXVm8Qq6I8JHzka2DdmwCHPiQ1P9IIwVDejLITn78weWuL/D5ZM+w Y7Y9spWLkobYO9bBBW+KoRCs+8rumUtl0wUdv5ueksGNZejpHk94dLA3KJtVcp5h PibeFKdkcafXMOwXqdZjckTeHnHorDG3pAkE8knXJX0oV4DTRdgmV8KNySCJiGkc mP6jJ8r2oRVF5g6G4H7mbMXHiuC0NHv+nZFtHhpDYtJE6Nq6Pgk2vewhrshRpbuw AVGwoWGPiW/SL98hdxIdFCyOAAG3aYfYUYXP+dwLPsUsVLIc9oLqC+T+jwARAQAB tDBEZWJyaWNrZWQgU2VjdXJpdHkgVGVhbSA8c2VjdXJpdHlAZGVicmlja2VkLmNv bT6JAk4EEwEIADgWIQQXVx4GqmV9KC42daP+latBnZd5XQUCYCvBBQIbAwULCQgH AgYVCgkICwIEFgIDAQIeAQIXgAAKCRD+latBnZd5XYVyD/wI09Cs2j3Sm/q0C5YN 57Ni1vbAQ3M+t1+e7m6gg8Z7RT/LxFwHhkrnrOdm7NJsogUre46fM6wQ0qbdqRkl vFMu54KMPV5VTKflz1HQ58//uooZsgagfPTwRfQGc4Hhd5QdDTIwBojH7EddqxWh kQr0S35DZtHrpkr8MCVCGF5CAzqRrwOfzcMcp7npMaxBNFQhbrAfWh+JkR48b1Bd oN9Qz/49HHoO5kBp2EEH3TEdw0I16jh8CPdPJ4yn0fq3UGUoXEW4G89CzhAlsfMn gp1C5oaUxqLVXvxYyWE/fFf3+CQElgmzCzoI+IfXkFLIdamIcYsUf3pSPxSuMQmy WnDYt6qMbbK4x+pXSfSk3SnagEwxV6uvt00qiPABn+jckHxoqFtsZbHeL2ZPbDAZ 1/rWbRqyxDrWkon+zOQKCu0rfKWbwg5F1AtATpDu+fIHyqvRZMoiGJqv9V3PuHof h+TvEHNBGTaZeor9k5lXuxdH0u0imFqIFTKzaRhmZu5RCfKewkCXZ6rMQ6bQE4Vw dRxGn7ya4U8d3bNnDm9B3Yij2MNEcCgiW6bDYtItNO+50JAzk2rwNEgIBeo1dhdp 181i/huy1sIDtJfQoRtFcvNRnKhPwZyuCQifP3Iiby19RFnvvzIlwRU6PV8ugxUF dp3rQWn4bMGHVir1G3UKbmy50LkCDQRgK8EFARAAvPWwr43MwT9kIzzJp4in1Htg bFY/EvDc6Agr8evb6VsbbmfIanRA4bxGDZ7jo2UNY3FRJeun96Jb1Y28pggrAAZp bvaOgVRehxCI0FBGOZs38UBYqSDHAzJdzyZ2O3KvQIEjeuznMw0YpBXXtGhi8ICi /XFMp9JeVPPmQsivQMYeUfVOxb5uAldEizacUobEXteLogX95Vgp8ArtWPVk0GP8 YVyH/mTes7LKld5pb+7awXL6npLmiSQt5An93WWwDQWvHaSQRtHkWU4yhH/Zfmtw uK6yPJy85v+eD0iHUJxF9UnDgEaloDknszr7IPI2vfWHAORW1gtJipWU2sQ/VinY y5Ew2vS/JDNup7G/MFG80QaXRs8CeEPaflAVEwOcfGFMop90kMXHJDJ/BvegSGLv gHS1PUz3Coulw0xB8RQyyYIkD1xEi9JFYBenV6P7CJoMARmTws3eBauBmhDx/1NE ODcGnKlN+sSgSBlpLT7+U9geeBxwt4jjueKKsZ3GUOO4RDYdMkvHdQzztjvoCI9H FKvA+O9sCMCOLTIR6Os6c4+EPuyLMUc4WU63S0mRLl4argomULgcrQ9V9Xn8T70G lgYXSZOZaeA0yT5FIcayAo6egr70pqxBL56EpL8lwfc2tMHTlwT1UMID+BjSGiOs cbJjtN6ncja/K3173c8AEQEAAYkCNgQYAQgAIBYhBBdXHgaqZX0oLjZ1o/6Vq0Gd l3ldBQJgK8EFAhsMAAoJEP6Vq0Gdl3ld6ncQALW0ZOISOsxYWT3kTy3KkMG7bl1h CJsm/k7ey3YmIUU9p8IegLpm+n95og/AehpJns0ZZX2WQjReHTEaasC3iLxzP9Tl b1grDcXKR5XoKphck4Bktqn74OkZHLxDsLGSXxFh4QYt+rX9nmnXbcymiwvW4VLg KC7p/SGTI4xcGfn7gPqGDPMqf8VIFfuH7fqdxkxBTKhiLw+0BxEA1wDNPvZypfSU Mp8Os9EP65LF+SOy377EUK8ZBusRHU7G/lHa9a+ryeCFIHzevndBgOFgDRkjvH6k E1Z32ZxIEGyedxoVVyM622zsm+aAF9QJYJa3e7s6nOU3sfMDeUBFSZNEvlc64p6q ORUMJxEkUxGOf8kn+N8vpi7rBxMy8+6vewZkswksJ4+r6IF+PDTGm4pQPSASIIwo e+YmyeeftqmjhNQRyiyqYmNA/2TEuNfyTWHXUUG8sMb0lYfYT2uh+vh2b3OeQ/aM CovwqT+7fOoH3JcC4O0cNZQpSkduhc0MebWSJw9AkroCjsBczCstLoWJokEaLpDb gkjGgqoL/6LWNV35VDTxT50bA2nGJwlUK9fP4/ewWdENklgPB8V3OAZZxPhuFEWm 4a7QJu6iHAesgjlmoZwQQ/q0Qr+NK/HuUwaD/BQCwgNMEmdQlZA32BgZePp8xLl3 7Ys6nMgu2ATezuS6 =E1f1


Security Hall of Fame

Debricked would like to thank the following security researchers for disclosing vulnerabilities to us in a responsible manner:

Sachin Kalkumbe@sachinkalkumbe42
Darshan Jogi@darshan_Jogi_2
Tuhin Bose@tuhin1729_2
Mayank Kamboj Dattana@Mayank_hacks1
Gaurav Popalghat@n008x1
Sakshi Patil@_sakshiPatil_1
Pankaj Desai@PankajD491144031
Hasibul Hasan Rifat@rifatsec1
Foysal Ahmed Fahim@foysal11971
Tushar Sharma@tusharSharma_01
Muskan Shaikh1
Girish B O@Girishbo051
Shreyas Koli@SPY8OY1
Dinesh Kumar@dhina__0161
Rk Thakur@cyberarmy1011
Keroles Magdy@Keroles__Magdy1
Nikhil Rane@nikran24991
Sarfraz Zahra@sarfraz_zahra_1