Vulnerability Scan Result
| Title: | Accueil - Planete Sports |
| Description: | No description found |
| ip_address | 83.166.133.66 |
| country | CH  |
| network_name | Infomaniak Network SA |
| asn | AS29222 |
21/tcp | ftp | ProFTPD - |
22/tcp | ssh | OpenSSH 8.4p1 Debian 5+deb11u6 |
80/tcp | http | Apache - |
443/tcp | https | Apache - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Clipboard.js | JavaScript libraries |
| Complianz 7.4.6 | A/B Testing, Cookie compliance, WordPress plugins |
| Contentsquare | Analytics, A/B Testing |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| Hello Elementor 3.4.7 | WordPress themes |
| Google Font API | Font scripts |
| FullCalendar 6.1.9 | Widgets |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.46.0 | JavaScript libraries |
| Google Analytics | Analytics |
| Apache HTTP Server | Web servers |
| imagesLoaded 5.0.0 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| Onsen UI | Mobile frameworks |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Select2 | JavaScript libraries |
| Site Kit 1.178.0 | Analytics, WordPress plugins |
| DoubleClick Floodlight | Advertising |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| WooCommerce 10.7.0 | Ecommerce, WordPress plugins |
| WordPress | CMS, Blogs |
| AMP | JavaScript frameworks |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| Hotjar | Analytics |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
| TypeScript | Programming languages |
| Yoast SEO 27.6 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.planete-sports.ch/ | wp_woocommerce_session_b0cb301a8b096af100993270212f314b | Set-Cookie: wp_woocommerce_session_b0cb301a8b096af100993270212f314b=t_bd6fca10c7d2e90273f04c47b2aec7%7C1778956376%7C1778869976%7C%24generic%24G0KU3p4evkcdLP_Fj0qzWpf4kb7AMoeqM0kdPdWF |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Clipboard.js | JavaScript libraries |
| Complianz 7.4.6 | A/B Testing, Cookie compliance, WordPress plugins |
| Contentsquare | Analytics, A/B Testing |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| Hello Elementor 3.4.7 | WordPress themes |
| Google Font API | Font scripts |
| FullCalendar 6.1.9 | Widgets |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.46.0 | JavaScript libraries |
| Google Analytics | Analytics |
| Apache HTTP Server | Web servers |
| imagesLoaded 5.0.0 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| Onsen UI | Mobile frameworks |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Select2 | JavaScript libraries |
| Site Kit 1.178.0 | Analytics, WordPress plugins |
| DoubleClick Floodlight | Advertising |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| WooCommerce 10.7.0 | Ecommerce, WordPress plugins |
| WordPress | CMS, Blogs |
| AMP | JavaScript frameworks |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| Hotjar | Analytics |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
| TypeScript | Programming languages |
| Yoast SEO 27.6 | SEO, WordPress plugins |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.planete-sports.ch/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.planete-sports.ch/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Credit Card Number: 2644536267352236 |
Vulnerability description
We noticed that this application does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. Sensitive data targeted usually consists of emails, credit card and social security numbers.
Risk description
The risk exists that sensitive personal information within the application could be accessed by unauthorized parties. This could lead to privacy violations, identity theft, or other forms of personal or corporate harm.
Recommendation
Compartmentalize the application to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-201 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.planete-sports.ch/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.planete-sports.ch/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 |
|
Vulnerability description
We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Risk description
The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.
Recommendation
Ensure that all external resources the page references are loaded using HTTPS.
Classification
| CWE | CWE-319 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.planete-sports.ch/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.planete-sports.ch/wp-content/uploads/2025/10 | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Cookies: wp_woocommerce_session_b0cb301a8b096af100993270212f314b=t_0abdd5bbe0896a9ff3b9f9ea191b10%7C1778956379%7C1778869979%7C%24generic%24wlZ5_d4gjOSu... | Possible API endpoint found at |
Vulnerability description
We found API endpoints while crawling the given web application.
Risk description
These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.
Recommendation
Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.planete-sports.ch/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: redaction@planete-sports.ch |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-05-14 21:33 EEST Nmap scan report for www.planete-sports.ch (83.166.133.66) Host is up (0.022s latency). Other addresses for www.planete-sports.ch (not scanned): 2001:1600:4:11::2d0 rDNS record for 83.166.133.66: h2web359.infomaniak.ch
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 8.4p1 Debian 5+deb11u6 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 0.81 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp ProFTPD
Vulnerability description
We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.
Risk description
Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.
Recommendation
We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.planete-sports.ch | A | IPv4 address | 83.166.133.66 |
| www.planete-sports.ch | AAAA | IPv6 address | 2001:1600:4:11::2d0 |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 5.4 | 98% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Onsen UI | Mobile frameworks |
| Amazon Web Services | PaaS |
| Apache HTTP Server | Web servers |
| Hello Elementor 3.4.7 | WordPress themes |
| WooCommerce 10.7.0 | Ecommerce, WordPress plugins |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| Yoast SEO 27.6 | SEO, WordPress plugins |
| Site Kit 1.178.0 | Analytics, WordPress plugins |
| Swiper | JavaScript libraries |
| imagesLoaded 5.0.0 | JavaScript libraries |
| Google AdSense | Advertising |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Contentsquare | Analytics, A/B Testing |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Onsen UI | Mobile frameworks |
| Amazon Web Services | PaaS |
| Apache HTTP Server | Web servers |
| Hello Elementor 3.4.7 | WordPress themes |
| WooCommerce 10.7.0 | Ecommerce, WordPress plugins |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| Yoast SEO 27.6 | SEO, WordPress plugins |
| Swiper | JavaScript libraries |
| imagesLoaded 5.0.0 | JavaScript libraries |
| Google AdSense | Advertising |
| Site Kit 1.178.0 | Analytics, WordPress plugins |
| Complianz 7.4.6 | A/B Testing, Cookie compliance, WordPress plugins |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Contentsquare | Analytics, A/B Testing |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.