Vulnerability Scan Result
| Title: | Cobaty | L'acte de bâtir une meilleure qualité professionnelle |
| Description: | COBATY est une association née en France en 1957 issue de la réflexion et de la volonté de Femmes et d’Hommes responsables, impliqués dans l’acte de bâtir. |
| ip_address | 84.16.76.207 |
| 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 |
|---|---|
| Tippy.js | JavaScript libraries |
| Magnific Popup 1.0.0 | JavaScript libraries |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| core-js 3.31.0 | JavaScript libraries |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| Apache HTTP Server | Web servers |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Slick | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Popper | Miscellaneous |
| Select2 | JavaScript libraries |
| Selectize | JavaScript libraries |
| Underscore.js 1.13.4 | JavaScript libraries |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| AddToAny | Widgets |
| Google Tag Manager | Tag managers |
| Lodash 1.13.6 | JavaScript libraries |
| HSTS | Security |
| RSS | Miscellaneous |
| Yoast SEO 22.3 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.cobaty-ge.ch/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Tippy.js | JavaScript libraries |
| Magnific Popup 1.0.0 | JavaScript libraries |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| core-js 3.31.0 | JavaScript libraries |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| Apache HTTP Server | Web servers |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Slick | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Popper | Miscellaneous |
| Select2 | JavaScript libraries |
| Selectize | JavaScript libraries |
| Underscore.js 1.13.4 | JavaScript libraries |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| AddToAny | Widgets |
| Google Tag Manager | Tag managers |
| Lodash 1.13.6 | JavaScript libraries |
| HSTS | Security |
| RSS | Miscellaneous |
| Yoast SEO 22.3 | 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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.cobaty-ge.ch/wp-content/themes/cobaty | 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 | Response has an internal server error status code: 500 |
Vulnerability description
We noticed that the target application's website does not properly handle or incorrectly manages exceptional conditions like Internal Server Errors. These errors can reveal sensitive information through their error messages. For instance, an error message could inadvertently disclose system paths or private application details.
Risk description
The risk exists that attackers could utilize information revealed in Internal Server Error messages to mount more targeted and effective attacks. Detailed error messages could, for example, expose a path traversal weakness (CWE-22) or other exploitable system vulnerabilities.
Recommendation
Ensure that error messages only contain minimal details that are useful to the intended audience, and nobody else. The messages need to strike the balance between being too cryptic and not being cryptic enough. They should not necessarily reveal the methods that were used to determine the error. Such detailed information can be used to refine the original attack to increase the chances of success. If errors must be tracked in some detail, capture them in log messages - but consider what could occur if the log messages can be viewed by attackers. Avoid recording highly sensitive information such as passwords in any form. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a username is valid or not.
Classification
| CWE | CWE-209 |
| 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).
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
| URL | Evidence |
|---|---|
| https://www.cobaty-ge.ch/ |
|
Vulnerability description
We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.
Risk description
The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.
Recommendation
Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.cobaty-ge.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: info@cobaty-ge.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 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.cobaty-ge.ch/wp-json/oembed/1.0/embed | GET | Query: url=https://www.cobaty-ge.ch/ 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 | Possible API endpoint found at |
| https://www.cobaty-ge.ch/wp-json/wp/v2/web-app-manifest | 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 | 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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-02-17 14:22 EET Nmap scan report for www.cobaty-ge.ch (84.16.76.207) Host is up (0.0081s latency). Other addresses for www.cobaty-ge.ch (not scanned): 2001:1600:4:13:3648:edff:fef6:6114 rDNS record for 84.16.76.207: h2web260.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.26 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| WP Rocket | Caching, WordPress plugins |
| Yoast SEO 22.3 | SEO, WordPress plugins |
| Google Tag Manager | Tag managers |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| Underscore.js 1.13.4 | JavaScript libraries |
| Slick | JavaScript libraries |
| Magnific Popup 1.0.0 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Analytics | Analytics |
| AddToAny | Widgets |
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 |
| Apache HTTP Server | Web servers |
| HSTS | Security |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| WP Rocket | Caching, WordPress plugins |
| Yoast SEO 22.3 | SEO, WordPress plugins |
| Slick | JavaScript libraries |
| Magnific Popup 1.0.0 | JavaScript libraries |
| Google Analytics | Analytics |
| AddToAny | Widgets |
| Tippy.js | JavaScript libraries |
| Selectize | JavaScript libraries |
| Select2 | JavaScript libraries |
| Lodash 1.13.6 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| core-js 3.31.0 | JavaScript libraries |
| Popper | 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.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 3.16 - 4.6 | 100% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.cobaty-ge.ch | A | IPv4 address | 84.16.76.207 |
| www.cobaty-ge.ch | NS | Name server | ns2.infomaniak.ch |
| www.cobaty-ge.ch | NS | Name server | ns1.infomaniak.ch |
| www.cobaty-ge.ch | MX | Mail server | 5 mta-gw.infomaniak.ch |
| www.cobaty-ge.ch | SOA | Start of Authority | ns1.infomaniak.ch. hostmaster.infomaniak.ch. 2024020901 10800 3600 605800 86400 |
| www.cobaty-ge.ch | AAAA | IPv6 address | 2001:1600:4:13:3648:edff:fef6:6114 |
| www.cobaty-ge.ch | SPF | Sender Policy Framework | "v=spf1 include:spf.infomaniak.ch ?all" |
| www.cobaty-ge.ch | CNAME | Canonical name | cobaty-ge.org |
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.