- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 4
- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- 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.
- Safe harbor
-
Partial
no live installations, infrastructure, or resources are tested or exploited without explicit permission of their owners (including the MyBB Project and the Community Forums)
- Hall of fame
-
Yes
With consent, authors of confirmed vulnerability reports are credited publicly in:
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 3 excluded.
Domains 1
- mybb.com
Source code 1
- https://github.com/mybb/mybb/tree/feature No bounty
Products and areas 2
- MyBB 1.8.x pre-release codebase
- MyBB 1.8.x releases
Out of scope (3)
- active MyBB installations not created to test such vulnerabilities
- themes or plugins
- the MyBB Project infrastructure or its resources
Rules
What the policy asks of you, and the bug types it won't reward, quoted from MyBB Group's policy. "We" in these lines means the program, not this site.
While testing
-
we urge you to not disclose any information related to your report to parties other than the MyBB Team through official communication channels until an official solution is published
-
You should not test, demonstrate or exploit the vulnerability on any active MyBB installations not created to test such vulnerabilities nor the MyBB Project infrastructure or its resources
-
we recommend using a local copy
-
Generated content (from LLMs, AI assistants, or similar tools) must be reviewed and disclosed
-
no live installations, infrastructure, or resources are tested or exploited without explicit permission of their owners
-
no details regarding the vulnerability are published before it has been addressed
Not accepted
-
vulnerabilities within third party extensions do not count
-
techniques such as social engineering or phishing do not count
-
disclosure of operational information included in PHP or SQL errors, spam attacks, bypassing CAPTCHAs, etc. do not count
-
vulnerabilities within development releases or older versions do not count
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.