Vulnerability Scan Result
| Title: | SWISS21 – Das digitale Ökosystem für Schweizer KMU |
| Description: | Mit der All-in-One-Lösung von Swiss21 erleichtern Sie die Verwaltung Ihres Unternehmens. Rechnungen, Offerten, Buchhaltung, Löhne uvm. | Jetzt kostenlos testen. |
| ip_address | 84.16.76.235 |
| country | CH  |
| network_name | Infomaniak Network SA |
| asn | AS29222 |
21/tcp | ftp | ProFTPD - |
22/tcp | ssh | OpenSSH 6.7p1 |
80/tcp | http | Apache - |
443/tcp | https | Apache - |
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Linkedin Insight Tag | Analytics |
| cdnjs | CDN |
| Contact Form 7 | WordPress plugins, Form builders |
| Magnific Popup 1.1.0 | JavaScript libraries |
| Facebook Pixel | Analytics |
| FitVids.JS 4.22.2 | Widgets, Video players |
| Font Awesome | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| Apache HTTP Server | Web servers |
| jQuery | JavaScript libraries |
| Slick | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Rich Plugins Reviews | WordPress plugins, Reviews |
| Underscore.js 1.13.4 | JavaScript libraries |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| WPML 4.6.5 | WordPress plugins, Translation |
| Cloudflare | CDN |
| CookieYes | Cookie compliance |
| Divi | Page builders, WordPress themes, WordPress plugins |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| RSS | Miscellaneous |
| Zendesk | Documentation, Issue trackers, Live chat |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2024-6386 | 9.9 | 0.68998 | 0.98571 | The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via the Twig Server-Side Template Injection. This is due to missing input validation and sanitization on the render function. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. |
| CVE-2025-3488 | 6.4 | 0.00032 | 0.08485 | The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_switcher shortcode in versions 3.6.0 - 4.7.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://old.swiss21.org/medien/ | PHPSESSID | Set-Cookie: PHPSESSID=ebb170e73f8ac7cc031cea4e91a60a01 |
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
| URL | Cookie Name | Evidence |
|---|---|---|
| https://old.swiss21.org/medien/ | PHPSESSID | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=ebb170e73f8ac7cc031cea4e91a60a01 |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| 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 | Evidence |
|---|---|
| https://old.swiss21.org/ | 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
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Linkedin Insight Tag | Analytics |
| cdnjs | CDN |
| Contact Form 7 | WordPress plugins, Form builders |
| Magnific Popup 1.1.0 | JavaScript libraries |
| Facebook Pixel | Analytics |
| FitVids.JS 4.22.2 | Widgets, Video players |
| Font Awesome | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| Apache HTTP Server | Web servers |
| jQuery | JavaScript libraries |
| Slick | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Rich Plugins Reviews | WordPress plugins, Reviews |
| Underscore.js 1.13.4 | JavaScript libraries |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| WPML 4.6.5 | WordPress plugins, Translation |
| Cloudflare | CDN |
| CookieYes | Cookie compliance |
| Divi | Page builders, WordPress themes, WordPress plugins |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| RSS | Miscellaneous |
| Zendesk | Documentation, Issue trackers, Live chat |
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
| URL | Evidence |
|---|---|
| https://old.swiss21.org/ | 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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://old.swiss21.org/ | 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 |
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.
Evidence
Vulnerability description
Website is accessible.
Evidence
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2024-6386 | 9.9 | 0.68998 | 0.98571 | No | The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via the Twig Server-Side Template Injection. This is due to missing input validation and sanitization on the render function. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. |
| CVE-2025-3488 | 6.4 | 0.00032 | 0.08485 | No | The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_switcher shortcode in versions 3.6.0 - 4.7.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
Vulnerability description
Vulnerabilities found for WPML 4.6.5
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-11-02 03:55 EET Nmap scan report for old.swiss21.org (84.16.76.235) Host is up (0.020s latency). rDNS record for 84.16.76.235: h2web286.infomaniak.ch
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 6.7p1 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1.44 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
| Operating System | Accuracy |
|---|---|
| Linux 3.16 - 4.6 | 100% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| old.swiss21.org | A | IPv4 address | 84.16.76.235 |
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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Sentry | Issue trackers |
| MySQL | Databases |
| PHP | Programming languages |
| Contact Form 7 5.8.1 | WordPress plugins, Form builders |
| FitVids.JS 4.22.2 | Widgets, Video players |
| Apache HTTP Server | Web servers |
| Amazon Web Services | PaaS |
| RankMath SEO | WordPress plugins, SEO |
| Microsoft Advertising | Advertising |
| Google Analytics GA4 | Analytics |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| WP Rocket | Caching, WordPress plugins |
| Divi | Page builders, WordPress themes, WordPress plugins |
| Cloudflare | CDN |
| WPML 4.6.5 | WordPress plugins, Translation |
| Rich Plugins Reviews | WordPress plugins, Reviews |
| Zendesk | Documentation, Issue trackers, Live chat |
| Slick | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Magnific Popup 1.1.0 | JavaScript libraries |
| Linkedin Ads | Advertising |
| cdnjs | CDN |
| CookieYes | Cookie compliance |
| Amazon S3 | CDN |
| Mouse Flow | Analytics |
| Lodash 1.13.6 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery 3.7.0 | JavaScript libraries |
| Isotope | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.239 | Analytics |
| core-js 3.19.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Google Font API | Font scripts |
| Font Awesome | Font scripts |
| RSS | Miscellaneous |
| PWA | Miscellaneous |
| Open Graph | Miscellaneous |
| Underscore.js 1.13.4 | 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.