If you discover a security flaw on Naivesy.com, please contact us as soon as possible. We will review all legitimate vulnerability reports and do everything possible to resolve the issue as soon as possible. Please review this document before reporting, including the fundamentals, bounty program, reward guidelines, and what should not be reported.
If you follow the principles outlined below when reporting a security issue to Naivesy.com, we will not file a lawsuit or initiate an enforcement investigation in response to your report.
We ask that:
You give us a reasonable amount of time to review and repair a haul you report before making any information about the report public or sharing it with others.
If the account owner has not consented to such actions, you do not interact with the account (including modifying or accessing data from the account).
You make a good faith effort to avoid violating others' privacy and causing disruptions to their lives, including (but not limited to) the destruction of knowledge and the interruption or degradation of our services.
You do not, under any circumstances, exploit a security flaw that you discover. (This includes demonstrating additional risk, such as attempting to compromise sensitive company data or looking for additional issues.)
You are not in violation of any other applicable laws or regulations.
Bounty Program
We recognize and reward security researchers who report vulnerabilities in our services and help us keep people safe. Monetary rewards for such reports are entirely at the discretion of Naivesy.com, based on risk, impact, and other factors. To be eligible for a bounty, you must first meet the following requirements:
  • Adhere to our fundamentals (see above).
  • Report a security bug: that's , identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that Naivesy.com ultimately determines the danger of a drag , which many bugs aren't security issues.)
  • Submit your report via our security center. Please don't contact employees.
  • If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating a haul , inform disclose this in your report.
  • We investigate and answer all valid reports. because of the number of reports we receive, though, we prioritize evaluations supported risk and other factors, and it's going to take a fast time before you receive a reply.
  • We reserve the proper to publish reports.
Our rewards are backed up by the impact of a vulnerability. We'll update the program based on user feedback, so please provide feedback on any aspect of the program you think we should improve.
  • Please provide detailed reports with reproducible steps. If the report isn't detailed enough to breed the matter , the matter won't be eligible for bounty.
  • When duplicates occur, we award the primary report that we'll completely reproduce.
  • Multiple vulnerabilities caused by one underlying issue are becoming to be awarded one bounty.
  • We determine bounty reward supported a selection of things , including (but not limited to) impact, simple exploitation, and quality of the report. We specifically note the bounty rewards, these are listed under.
  • Amounts below are the utmost we'll pay per level. We aim to be fair, all reward amounts are at our discretion. Critical severity Vulnerabilities ($200): Vulnerabilities that cause a privilege escalation on the platform from unprivileged to admin, allows remote code execution, financial theft, etc.
  • Remote Code Execution
  • Remote Shell/Command Execution
  • Vertical Authentication bypass
  • SQL Injection that leaks targeted data
  • Get full access to accounts
High severity Vulnerabilities ($100): Vulnerabilities that affect the safety of the platform including the processes it supports.
  • Lateral authentication bypass
  • Disclosure of important information within the corporate
  • Stored XSS for a further user
  • Local file inclusion
  • Insecure handling of authentication cookies
  • Medium severity Vulnerabilities ($50): Vulnerabilities that affect multiple users, and need little or no user interaction to trigger.
  • Common logic design flaws and business process defects
  • Insecure object of the verb References
  • Low severity Vulnerabilities: Issues that affect singular users and need interaction or significant prerequisites (MITM) to trigger.
  • Open redirect
  • Reflective XSS
  • Low sensitivity Information leaks


Customer Support 24/7
Email: Support@naivesy.com
Phone: +1 (917) 672 8439