Standup & Prosper
Vulnerability disclosure program on Self-hosted standup-and-prosper.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 2
- 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 as the policy says
- The policy page explains how.
- 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.
Scope
2 assets you may test, 6 excluded.
Domains 1
- standup-and-prosper.com
Wildcard domains 1
- standup-and-prosper.com domains
Out of scope (6)
- Any bugs in operating systems or hardwares
- Bugs in third party libraries used by our open source solutions
- Bypassing XSS
- Our customer's domains and services
- Platforms we integrate with our out of scope--(e.g.Discord, Slack, Teams, etc)
- URL preview and email spoofing
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Standup & Prosper's policy. "We" in these lines means the program, not this site.
While testing
-
Do not disclose the details of the vulnerability until we fix the vulnerability and the fix is released to most users
-
Do not engage in any activity that would be disruptive or damaging to other users
-
Publicly disclosed information related to the security disclosure before it is fixed and rolled out to all customers, will result in penalities and legal action.
-
Rhosys employees cannot participate this program
Not accepted
-
Bypassing XSS is out-of-scope or other UI related issues are out of scope.
-
URL preview and email spoofing is out-of-scope
-
Any bugs in operating systems or hardwares
-
Bugs not reproducible on the latest version of user browsers, SDKs, or dependent services.
-
Bugs that are already reported by other participant, or aware by internal reviews
-
Public bugs
-
Theoretical vulnerabilities without proof of concept
-
Simple crash by an assertion or Denial-of-Service (DoS) attack
-
Vulnerabilities occurred when manually disabling security features
-
Bugs in experimental features
-
Bugs that are already reported to third parties
-
Bugs that require a user device takeover
-
Bugs that you have disclosed publicly
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.