Incident Response & Disclosure
How to report a security vulnerability in FundlyHub, and what we do when a security incident happens.
Report a vulnerability
Reporting a campaign instead? See Safety.
If you believe you have found a security vulnerability in FundlyHub, please report it responsibly, by email. We appreciate your help in keeping our platform and users safe.
Your report
What to put in the email, and which issues are in scope.
Subject line
Start with [SECURITY], then a brief description of the issue.
What to include
- A description of the vulnerability
- Its potential impact
- Steps to reproduce, or a proof of concept
- The affected URL, endpoint or component
- Your contact information, for follow-up
- Any suggested fixes (optional)
In scope
Authentication or authorization bypass, cross-site scripting (XSS), SQL injection, remote code execution, sensitive data exposure, cross-site request forgery (CSRF) and server-side request forgery (SSRF).
Out of scope
Social engineering attacks, denial of service (DoS or DDoS), issues in third-party services, and issues requiring physical access.
After you report
What you can expect from us, and when.
Step 1You report it
Email security@fundlyhub.org with the details above.
Within 24 hoursWe acknowledge it
We confirm that we received your report.
Within 72 hoursWe assess it
We complete an initial assessment of your report.
Within 7 daysYou get a status update
We tell you where your report stands.
Within 7, 30 or 90 daysWe resolve it
Critical: within 7 days.
High: within 30 days.
Medium or low: within 90 days.On resolutionWe tell you it is fixed
We notify you once the issue is resolved.
Severity levels
How we classify a security incident.
P1: Critical
Active data breach or total service outage.
Examples: database exposure, credential compromise.
P2: High
Partial degradation or unauthorized access risk.
Examples: authentication bypass, API abuse, failed backup.
P3: Medium
Security misconfiguration or vulnerability.
Examples: open port, unpatched critical CVE.
P4: Low
Informational events or failed attacks.
Examples: port scan, phishing attempt.
When an incident happens
Five steps, in this order.
- 01
Detect and identify
We acknowledge the alert and assess its severity, using the levels above. One person takes charge of the response. Alerts come from our error monitoring (Sentry).
- 02
Contain
We isolate the affected systems. As needed, credentials are revoked, IP addresses are blocked and services are taken offline. Evidence is preserved before any fix is made.
- 03
Eradicate
We remove the root cause: a patch, a credential rotation or a configuration fix.
- 04
Recover
We restore services and verify the fix with health checks.
- 05
Post-incident review
We hold a review within 5 business days and document the root cause, the timeline and the lessons learned. Controls and runbooks are updated.
If personal data is affected
Affected users
Notified within 72 hours if personal data is compromised.
Relevant authorities
Contacted per applicable regulations.
More in the Trust Center
Security questions: security@fundlyhub.org