Skip to content

Moov

By MOOV Financial Vulnerability disclosure program on HackerOne moov.io

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
7
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 on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

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

7 assets you may test, 5 excluded.

Web 7

  • api.moov.io Critical No bounty
  • cards.moov.io Critical No bounty
  • dashboard.moov.io Critical No bounty
  • gateway.moov.io Critical No bounty
  • infra-oss.moov.io Critical No bounty
  • moov.io Critical No bounty
  • oss.moov.io Critical No bounty
Out of scope (5)
  • email-zendesk
  • slack.moov.io
  • support.moov.io
  • tools.cards.moov.io
  • tools.moov.io

Rules

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

While testing

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the MOOV Financial.

Not accepted

  • 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.
  • 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 on non-authentication endpoints
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • 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 17 minutes 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.

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.

#Brand Promise

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

#Scope

This policy applies to any digital assets, owned, operated, or maintained by Moov, including public facing websites.

#Out of Scope

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

  • 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.
  • 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 on non-authentication endpoints
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction

#Disclosure Policies

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

#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 MOOV Financial and our users safe!