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

• Only use the 3 EAN's giving in the In Scope section when placing test orders
• Provide detailed but to-the point reproduction steps
• Include a clear attack scenario. How will this affect us exactly?
• Remember: quality over quantity!
• Reports should be written in English
• Please do not discuss or post vulnerabilities without our consent (including PoC's on places like, but not limited to, 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 😉)

At vidaXL, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present. If you discover a vulnerability, we would like to know about it, so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

For us it is important, that our whole webshops are being checked extensively (like homepage, product listing pages, product detail page, cart page, myaccount pages, login page, checkout page, thank you page, etc. and the different functionalities on them (f.e. loyalty programme, payment service provider, etc).

Please take into account the following rules:

Only use the following 3 EAN's when placing test orders

8718475559313
8718475616184
8718475719380
(f.e. www.vidaxl.xx/e/8718475559313) (in case of violation, no bounty can be awarded). These are product EANs for products you can use to test.
Note: not all EANs are avaiable on all webshops, as assortment can be different per webshop.

Shared codebase disclaimer:

All shops (TLDs) in scope use the same code-base and backend. If a specific issue has already been found in another vidaXL shop the report will be regarded as a duplicate.

Salesforce Assets

For Salesforce assets, the following rules apply: https://help.salesforce.com/articleView?id=000356579&type=1&mode=1

Thank you for browsing our pages and helping protect our shop and our customers!

Domains

• partners.vidaxl.com

Application

• API key disclosure without proven business impact
• Wordpress usernames disclosure
• 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 flags
• 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 without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks are not sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

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
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, 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
• Reports that state that software is out of date/vulnerable without a proof-of-concept

This programs follows Intigriti's contextual CVSS standard.

Where can we get credentials for the app?

You can self-register on the application but please don’t forget to use your @intigriti.me address.