Bug Bounty Program
Thank you for your interest in helping us improve the security of our open source products, websites and other properties.
We have created this Bug Bounty program to appreciate and reward your efforts.
We base all payouts on impact and will reward accordingly. Please emphasize the impact as part of your submission. We are particularly interested and will consider extraordinary submissions for issues that result in full compromise of a system.
|Critical||$500 to $5000+ depending on severity|
|Low||Case to case|
|Common in all of above||Certificate of appreciation + inclusion in our hall of fame|
The table above outlines the nominal rewards for in-scope assets. Brainstorm Force, at its own discretion, will make a final decision on the bounty for qualifying vulnerabilities. Bounties will be awarded to the first reporter of a vulnerability only.
Amounts may vary depending upon the severity of the issue and quality of the report.
|Brainstorm Force Store||https://store.brainstormforce.com/|
|Astra||WordPress theme (https://wordpress.org/themes/astra/)|
|License and Updates APIs||https://support.brainstormforce.com|
|Starter Templates||WordPress plugin (https://wordpress.org/plugins/starter-templates/)|
|Ultimate Addons for Gutenberg||WordPress plugin (ultimategutenberg.com)|
|Ultimate Addons for elementor||WordPress Plugin (ultimateelementor.com)|
|Schema Pro||WordPress Plugin (wpschema.com)|
|Convert Pro||WordPress Plugin (www.convertpro.net)|
|WP Portfolio||WordPress Plugin (wpportfolio.net)|
|Convert Plus||WordPress Plugin (convertplug.com/plus/)|
|Ultimate Addons for WPBakery Page Builder||WordPress plugin (ultimate.brainstormforce.com)|
|Multipurpose Before After Slider||WordPress Plugin (baslider.brainstormforce.com)|
|CartFlows||CartFlows WordPress plugin (cartflows.com, my.cartflows.com)|
|ProjectHuddle||WordPress plugin – https://wordpress.org/plugins/projecthuddle-child-site/|
If you believe you have found a bug in our property that is not mentioned in the scope above, and would like to report it: please send us an email on [email protected] and we’re happy to confirm.
As we’re a growing organization, we might have a property that was built recently and is missed out from the list above.
Vulnerability reports which will not include manual validation – for example, reports based only on results from automated tools and scanners or which describe theoretical attack vectors without proof of exploitability – will be rejected.
Indicate steps to reproduce and verify you demonstrate a working proof of concept.
Submissions without sufficient details – will be rejected.
Since we use same stack for all the websites, a vulnerability which exists across all the websites will be considered one report when it comes for a bounty.
Any reproducible vulnerability that affects the security of our users is likely to be in scope for the program. Common examples include:
- Cross Site Scripting (XSS)
- Cross Site Request Forgery (CSRF)
- Server Side Request Forgery (SSRF)
- Remote Code Execution (RCE)
- SQL Injection (SQLi)
- Privilege Escalation
- We are generally not interested in DoS vulnerabilities that are perceived by a lack of rate-limiting or captcha. As a web-scale service, our threshold for rate limiting is higher than you would probably expect. Of course, if you think you have found an exception to this rule, please let us know.
- Any contact or support forms
- Anything SSL (related attacks, insecure cipher suites, etc.)
- Weak Captcha / Captcha Bypass
- Username / Email Enumeration
- Brute Force attacks on our Login or Forgot Password pages
- Account lockout enforcement and related attacks
- HTTP security headers and Cookies related Issues
- Weak password policies
- CSRF on forms that are available to anonymous users (e.g. login or contact forms)
- Anything related to Mail Server Domain Misconfiguration (Email spoofing, missing DMARC, SPF/DKIM, etc.)
- Vulnerabilities impacting only old or end-of-life platforms, browsers and plugins
- Cross Site Scripting (XSS) is out of scope for all impactless domains.
- Missing Best Practices that don’t pose a direct security threat will most likely not be accepted.
- We are generally not looking for any reports for our marketing/product websites and would rather prefer reports for the actual products. That being said, If you believe some vulnerability is serious do report it to us, although our security team will review and decide the severity of the report for websites from our prespective.
Crafting a Report:
If our team cannot reproduce and verify an issue, a bounty cannot be awarded. To help streamline our intake process, we ask that submissions include:
- Description of the vulnerability
- Steps to reproduce the reported vulnerability
- Proof of exploitability (e.g. screenshot, video)
- Perceived impact to another user or the organization
- Proposed CVSSv3 Vector & Score (without environmental and temporal modifiers)
- List of URLs and affected parameters
- Other vulnerable URLs, additional payloads, Proof-of-Concept code
- Browser, OS and/or app version used during testing
- Impact of the bug
Security reports should be sent to [email protected]
Once again, thank you for helping us improve security. We really appreciate it.