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

Raidboxes

Vulnerability disclosure program on Self-hosted raidboxes.io

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
11
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.
Replies within 5 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

This program does not pay cash rewards.

Pays cash
No We cannot pay you any monetary reward for finding potential or confirmed vulnerabilities.
Response
Within 5 days Within 5 business days (Mo-Fr), we will acknowledge that your report has been received.
Safe harbor
Full Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy.
Hall of fame
Yes Those who have discovered the vulnerability will have their name or alias listed below in the Hall Of Fame section below.

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

Scope

11 assets you may test, 3 excluded.

Domains 5

  • myraidbox.de
  • myrdbx.io
  • raidboxes.de
  • raidboxes.io
  • raidboxes.net

Wildcard domains 5

  • *.myraidbox.de
  • *.myrdbx.io
  • *.raidboxes.*
  • *.raidboxes.io
  • *.raidboxes.net

Web 1

  • https://dashboard.raidboxes.de
Out of scope (3)
  • Boxes (WordPress instances) that are not your own or have not been created by you.
  • Third party tools & services
  • WordPress Plugins and Themes that are not maintained by Raidboxes.

Rules

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

While testing

  • Do not compromise the privacy or safety of our customers.
  • Do not interrupt or degrade our services. Volumetric attacks of any kind (D/DoS, Brute-forcing etc. are not permitted)
  • Do not initiate fraudulent transactions.
  • Do not modify or access data that doesn’t belong to you.
  • We are looking for technical vulnerabilities , not human errors, so anything remotely related to phishing or any form social engineering is not in scope.
  • Reports from automated tools or scans that haven’t been manually validated
  • Provide enough detail to reproduce and validate the vulnerability, including targets, steps, tools, and artifacts.
  • Allow a reasonable amount of time for us to address the vulnerability before requesting an update or taking further action.

Not accepted

  • Accessible non-sensitive files and directories (for example: README.TXT, CHANGES.TXT, robots.txt, gitignore , etc.).
  • Issues only available in self-exploitation scenarios (e.g. self XSS or pasting JavaScript into the browser console).
  • Email spoofing (including lack of SPF, DMARC, DKIM , From: spoofing , and visually similar and related issues).
  • Descriptive error messages (for example: stack traces, application or server errors, path disclosure ).
  • Clickjacking and issues only exploitable through clickjacking.
  • CSRF issues that don’t impact the integrity of an account (for example: login or out, contact forms and other publicly accessible forms).
  • Lack of Secure and HTTPOnly cookie flags .
  • Missing HTTP security headers .
  • CORS misconfiguration on non-sensitive endpoints.
  • TLS/SSL Issues, including BEAST, BREACH, insecure renegotiation, bad cipher suite, expired certificates .
  • Out-of-date software / Software version disclosure.
  • Previously reported vulnerabilities are not eligible for an Hall Of Fame entry.

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.