Skip to content

Inspectorio

Bug bounty on HackerOne inspectorio.com

Accepting reports Full safe harbor
Top reward
$3,000
Top severity paid
Critical
Assets in scope
11
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $3,000
for critical bugs.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $3,000
High $1,500
Medium $500
Low $150
Response
Within 5 days Time to first response (from report submit) - 5 business days
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

11 assets you may test.

Web 9

  • api.stg.inspectorio.com Critical
  • app.stg.inspectorio.com Critical
  • docuflow.stg.inspectorio.com Critical
  • files-stg.inspectorio.com Critical No bounty
  • https://collabora.stg.inspectorio.com Critical No bounty
  • id.stg.inspectorio.com Critical
  • report-html-sight.stg.inspectorio.com Critical
  • rise-api.stg.inspectorio.com Critical
  • rise.stg.inspectorio.com Critical

Android apps 1

  • https://app.bitrise.io/app/51a95edaab331ec5/installable-artifacts/48548bd7878361ab/public-install-page/82f78f6dddbebab09e2f4ac3c0081984 Critical

iOS apps 1

  • https://testflight.apple.com/join/vwFxXX7t Critical

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Inspectorio (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
  • Please note, the sign-up service is not for hacking

Not accepted

  • IDOR vulnerabilities
  • Vertical privilege escalation
  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • 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
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • 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).
  • Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 30 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Rules updated

    Added: “[Inspectorio Academy](https://academy.inspectorio.com) to get more about SIGHT and RISE products. Academy access is provisioned per researcher: request it throu...”

  2. Scope added

    https://collabora.stg.inspectorio.com

  3. Scope added

    app.stg.inspectorio.com

  4. Scope added

    docuflow.stg.inspectorio.com

  5. Scope added

    files-stg.inspectorio.com

  6. Scope added

    https://app.bitrise.io/app/51a95edaab331ec5/installable-artifacts/e5213e1a814bf0ba/public-install-page/bed0d33f048271d6828c5a4a979ecc96

  7. Scope added

    https://testflight.apple.com/join/vwFxXX7t

  8. Scope added

    id.stg.inspectorio.com

  9. Scope added

    report-html-sight.stg.inspectorio.com

  10. Scope added

    rise-api.stg.inspectorio.com

  11. Scope added

    rise.stg.inspectorio.com

  12. Scope added

    api.stg.inspectorio.com

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

INSPECTORIO looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

INSPECTORIO will make a best effort to meet the following response targets for hackers participating in our program:

  • Time to first response (from report submit) - 5 business days
  • Time to triage (from report submit) - 7 business days
  • Time to bounty (from triage) - 7 business days

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Follow HackerOne's disclosure guidelines.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Test Plan

Please register here to get your account. Please note, the sign-up service is not for hacking

Upon logging on to the sites, you can click on the “Need Help” button to access the features navigation guide and walk through provided on the platform.

Documentation

  • RISE API Documentation
  • SIGHT API Documentation
  • Inspectorio Academy to get more about SIGHT and RISE products. Academy access is provisioned per researcher: request it through this program from the same @wearehackerone.com or @maildrop.cc address you used to register above, and we will create an individual account for you. We no longer issue a shared Academy login.

Focus area & Rewards

We are particularly interested in the following types of vulnerabilities, but you are not limited to these types only. We will reward reports based on severity per CVSS. For example:

Severity Vulnerability Reward
Critical Remote Code Execution $3000
High Arbitrary File Read $1500
SQL Injection $1500
XML External Entity (XXE) Processing $1500
Server-Side Request Forgery (SSRF) $1500
Medium XSS $500

We also accept the reports about disclosure of company credentials(passwords, api-keys, secrets) in public places. In this case the reward depends on the severity and impact(how bad is it?)

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • IDOR vulnerabilities
  • Vertical privilege escalation
  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • 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
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • 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).
  • Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep INSPECTORIO and our users safe!