- Top reward
- Not published
- 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.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- https://www.gofundme.com/c/security
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
Researchers are eligible for payment upon accepted unknown findings.
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, 7 excluded.
Domains 4
- api.gofundme.com
- funds.gofundme.com
- gateway.gofundme.com
- gofundme.com
Out of scope (7)
- charity.gofundme.com
- charitysandbox.gofundme.com
- charitysupport.gofundme.com
- community.gofundme.com
- fastly.gofundme.com
- happiness.gofundme.com
- support.gofundme.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from GoFundMe's policy. "We" in these lines means the program, not this site.
While testing
-
By providing a submission, you agree that you may not publicly disclose your findings or the contents of your submission to any third parties without GoFundMe’s prior written approval.
Not accepted
-
DoS/DDoS
-
Reports of spam
-
Social engineering
-
Unconfirmed reports from automated vulnerability scanners
-
Disclosure of server or software version numbers
-
Hypothetical sub-domain takeovers without supporting evidence
-
Perceived security weaknesses without concrete evidence of the ability to compromise a user (e.g., missing rate limits, missing headers, etc.)
-
Reports exploiting the behavior of, or vulnerabilities in, outdated browsers
-
User/merchant enumeration
-
Best practice reports without a valid exploit (e.g. use of “weak” TLS ciphers)
-
Disclosure of known public files or directories (e.g. robots.txt)
-
Domain Name System Security Extensions (DNSSEC) configuration suggestions
-
Banner disclosure on common/public services
-
Lack of Secure/HTTPOnly flags on non-sensitive cookies
-
Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality
-
Sender Policy Framework (SPF) configuration suggestions
-
CSRF
-
Contact us Form
-
Messaging
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 3 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.