Description

Since 2010, Speakap has helped more than 400 companies across 120 countries, 42 languages, and many time zones, reach their full potential with more productive employees. With an award-winning, easy-to-use employee app, Speakap empowers company leaders to share the right content with the right people at the right time. Speakap boasts very high adoption rates with users logging in almost 6x a day for 50+ seconds per time.

Bounties

Responsible disclosure

Rules of engagement
Not applicable
Not applicable
Not applicable
Not applicable

Our promise to you

  • We are happy to respond to any questions, please use the button in the right top corner for this.
  • We respect the safe harbour clause that you can find below

Your promise to us

  • Provide detailed but to-the point reproduction steps
  • Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!
  • Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
  • Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)
Domains

*.speakap.com

No Bounty
URL

*.speakap.io

No Bounty
URL

Any related Speakap domain

No Bounty
URL
No Bounty
iOS
No Bounty
Android
In scope

We are particularly interested, but not limited to, find out how one can exploit our system to:

  • Horizontal or vertical privilege escalation
  • RCE
  • SQL injection
Out of scope

Application

  • Pre-auth account takeover / oauth squatting
  • Self-XSS that cannot be used to exploit other users 
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non sensitive endpoints
  • Missing cookie flag
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms.
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking on pages without sensitive actions
  • CSV Injection
  • Host header injection without proven business impact
  • Blind SSRF without proven business impact (DNS pingback only is not sufficient)
  • Disclosed and/or misconfigured Google API key (including maps)
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing /Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing API keys without proven impact
  • Subdomain takeover without taking over the domain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Same Site Scripting Attack

General

  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • Attacks requiring the usage of shared computers, man in the middle or compromised user accounts
  • Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty.
  • Attacks requiring unrealistic user interaction
  • For submissions that apply for a large number of endpoints due to a structural misconfiguration, only the first report will be accepted. The others will be marked as a duplicate.
  • SAML integrations
  • Third party applications (the speakap 'developer platform')
  • Third party plugins for speakap
  • Vulnerabilities that bypass the premium subscription fee
Severity assessment

This program follows Intigriti's contextual CVSS standard

FAQ

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid Intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Program specifics
no reputation No collaboration
Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Overall stats
submissions received
63
average payout
N/A
accepted submissions
6
total payouts
N/A
Activity
11/14
Speakap
closed a submission
11/9
logo
created a submission
10/17
Speakap
closed a submission
10/15
logo
created a submission
9/28
Speakap
accepted a submission
8/14
logo
created a submission
5/10
Speakap
closed a submission
5/10
Speakap
accepted a submission
5/10
Speakap
closed a submission
5/9
Speakap
closed a submission