Snapshot 173985
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
Contact: mailto:security@spendesk.com Expires: 2027-10-01T00:00:00.000Z Preferred-Languages: en, fr Bug-Bounty: True Canonical: https://www.spendesk.com/.well-known/security.txt Last-Update: 2026-10-28T21:26:02Z # Bug bounty program # Scope: app.spendesk.com, api.spendesk.com # DO NOT USE automated scanners or tools that generate large amount of network traffic. # Please adhere to the additional following rules while performing research on this program: # Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through the contact mentioned above # Denial of service (DoS) attacks on Spendesk applications, servers, networks or infrastructure are strictly forbidden. # Avoid tests that could cause degradation or interruption of our services. # DO NOT USE automated scanners or tools that generate large amount of network traffic. # Do not leak, manipulate, or destroy any user data or files in any of our applications/servers. # Do not copy any files from our applications/servers and disclose them. # No vulnerability disclosure, full, partial or otherwise, is allowed. # General requirement # Always send a working proof of concept for any vulnerability you find. # If possible, include the CVSS score. # Maximum rewards for each type of vulnerability # Critical vulnerability: 2000 euros # High-risk vulnerability: 500 euros # Medium-risk vulnerability: 200 euros # Low-risk vulnerability: 50 euros # Reward eligibility # We are happy to thank everyone who submits valid reports which help us improve the security of Spendesk, however only those that meet the following eligibility requirements may receive a monetary reward: # You must be the first reporter of a vulnerability. # You must not be a former or current employee of Spendesk or one of its contractor (please refer to the internal bug bounty) # The report must be in english language. # The vulnerability must be a qualifying vulnerability (see below). # The report must contain the following elements: # Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and Spendesk # Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact # Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc # You must not break any of the testing policy rules listed above # Qualifying vulnerabilities # - Remote code execution (RCE) # - Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA) # - Code injections (HTML, JS, SQL, ...) # - Cross-Site Scripting (XSS) # - Open redirect with real security impact # - Broken authentication & session management # - Insecure direct object references # - Horizontal privilege escalation allows access to objects of other organizations # - Horizontal or vertical privilege escalation that allows access (CRUD) to objects of the same organization with a real security impact # - Clickjacking/UI redressing # - Sensitive information disclosure # Non-qualifying vulnerabilities # - Known CVEs without working PoC or outdated libraries without a demonstrated security impact # - Self-XSS or XSS that cannot be used to impact other users # - Stack traces or path disclosure # - Physical or social engineering attempts # - Missing security-related HTTP headers or cookie flags which do not lead directly to a vulnerability # - Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated # - Product flow and decisions about email update and password reset. # - Tabnabbing # - Mixed content warnings # - Clickjacking/UI redressing # - Denial of Service (DoS) attacks # - Open ports without real security impact # - Presence of autocomplete attribute on web forms # - Vulnerabilities affecting outdated browsers or platforms # - Expired certificate, best practices and other related issues for TLS/SSL certificates # - Reports with attack scenarios requiring MITM or physical access to victim's device # - Cross-Site Request Forgery (CSRF) # - Invalid or missing SPF (Sender Policy Framework), DKIM, DMARC records # - Session expiration policies (no automatic logout, invalidation after a certain time or after a password change) # - CSV injection without real security impact # - Blind SSRF without direct impact (e.g. DNS pingback) # - Lack of rate-limiting, brute-forcing or captcha issues # - User enumeration (email, alias, GUID, phone number) # - Password requirements policies (length / complexity / reuse) # - Ability to spam users (email / SMS / direct messages flooding) # - Disclosed / misconfigured Google API key (including Google Maps) # - Recently disclosed 0-day vulnerabilities (less than 30 days since patch release) # - Password reset token leak on trusted third-party website via Referer header (eg Google Analytics, Facebook…) # - Open redirect without real security impact # - Invalid or missing SPF (Sender Policy Framework) records (Incomplete or missing SPF/DKIM/DMARC)