Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

VanMoof

Vulnerability disclosure program on Self-hosted vanmoof.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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 by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.

Rewards

What the company's own policy page says it pays.

The policy link is dead. The page answered "not found" when we checked on 12 Nov 2026, and the company's security.txt does not point to a new one. The program may have moved or closed; confirm on the company's site before you test.

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 company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

1 asset you may test, 22 excluded.

Domains 1

  • vanmoof.com
Out of scope (22)
  • Any activity that could lead to the disruption of our service (DoS).
  • Attacks requiring MITM or physical access to a user's device.
  • Clickjacking on pages with no sensitive actions.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.
  • In-store security or physical facilities.
  • Missing best practices in Content Security Policy.
  • Missing best practices in SSL/TLS configuration.
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Missing HttpOnly or Secure flags on cookies.
  • Open redirect - unless an additional security impact can be demonstrated.
  • Policies as opposed to implementations - email verification, password length or reuse, etc..
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Rate limiting or bruteforce issues on non-authentication endpoints.
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Spam (unless a specific vulnerability leads to easily sending spam).
  • Tabnabbing
  • Third-party applications we make use of, but do not control. (e.g. a blog hosted on an external service - unless we've configured the blog in such a way as to make our in-scope areas vulnerable).
  • Vulnerabilities in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on vanmoof.com or related apps).
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version].
  • Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts).

Rules

What the policy asks of you, and the bug types it won't reward, quoted from VanMoof'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 may not be triaged.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • 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 explicit permission of the account holder.

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.
  • 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 on non-authentication endpoints.
  • 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).
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated.
  • In-store security or physical facilities.
  • Spam (unless a specific vulnerability leads to easily sending spam).
  • Policies as opposed to implementations - email verification, password length or reuse, etc..
  • Vulnerabilities in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on vanmoof.com or related apps).
  • Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts).

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours 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.