Vulnerability Scan Result
| Title: | The Leading Content Marketing Agency for the Risk&Insurance Industry - The INGAGE Institute |
| Description: | No description found |
| ip_address | 83.166.138.5 |
| 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 |
|---|---|
| anime.js 3.1.0 | JavaScript graphics |
| Calendly | Appointment scheduling |
| Contact Form 7 5.3.2 | WordPress plugins, Form builders |
| FitVids.JS 1.1.0 | Widgets, Video players |
| Flickity | JavaScript libraries |
| LazySizes | JavaScript libraries, Performance |
| waitForImages | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| core-js 3.36.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| GSAP 3.2.4 | JavaScript frameworks |
| Highlight.js | JavaScript libraries |
| Apache HTTP Server | Web servers |
| imagesLoaded 3.2.0 | JavaScript libraries |
| Isotope | JavaScript libraries |
| jQuery 1.12.4 | JavaScript libraries |
| lit-element 4.1.1 | JavaScript libraries |
| Google Maps | Maps |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Reveal.js | JavaScript frameworks |
| Twitter Emoji (Twemoji) 12.1.3 | Font scripts |
| WordPress 5.4.19 | CMS, Blogs |
| wpBakery | Page builders, WordPress plugins |
| WPMU DEV Smush 3.8.2 | WordPress plugins |
| CookieYes | Cookie compliance |
| WOW 0.3.6 | JavaScript frameworks, Web frameworks, JavaScript graphics |
| Google Tag Manager | Tag managers |
| Lodash 1.8.3 | JavaScript libraries |
| MediaElement.js 4.2.12 | Video players |
| Max Mega Menu 2.9.2 | Widgets, WordPress plugins |
| HSTS | Security |
| RSS | Miscellaneous |
| Slider Revolution 6.2.2 | Widgets, Photo galleries |
| Yoast SEO 14.1 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.36851 | 0.97101 | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-11022 | 6.9 | 0.03251 | 0.87007 | In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2019-11358 | 6.1 | 0.02717 | 0.85781 | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
| CVE-2015-9251 | 6.1 | 0.27164 | 0.96333 | jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed. |
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 | Evidence |
|---|---|
| https://ingage.institute/ | 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 | Evidence |
|---|---|
| https://ingage.institute/ | 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 |
|---|---|
| anime.js 3.1.0 | JavaScript graphics |
| Calendly | Appointment scheduling |
| Contact Form 7 5.3.2 | WordPress plugins, Form builders |
| FitVids.JS 1.1.0 | Widgets, Video players |
| Flickity | JavaScript libraries |
| LazySizes | JavaScript libraries, Performance |
| waitForImages | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| core-js 3.36.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| GSAP 3.2.4 | JavaScript frameworks |
| Highlight.js | JavaScript libraries |
| Apache HTTP Server | Web servers |
| imagesLoaded 3.2.0 | JavaScript libraries |
| Isotope | JavaScript libraries |
| jQuery 1.12.4 | JavaScript libraries |
| lit-element 4.1.1 | JavaScript libraries |
| Google Maps | Maps |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Reveal.js | JavaScript frameworks |
| Twitter Emoji (Twemoji) 12.1.3 | Font scripts |
| WordPress 5.4.19 | CMS, Blogs |
| wpBakery | Page builders, WordPress plugins |
| WPMU DEV Smush 3.8.2 | WordPress plugins |
| CookieYes | Cookie compliance |
| WOW 0.3.6 | JavaScript frameworks, Web frameworks, JavaScript graphics |
| Google Tag Manager | Tag managers |
| Lodash 1.8.3 | JavaScript libraries |
| MediaElement.js 4.2.12 | Video players |
| Max Mega Menu 2.9.2 | Widgets, WordPress plugins |
| HSTS | Security |
| RSS | Miscellaneous |
| Slider Revolution 6.2.2 | Widgets, Photo galleries |
| Yoast SEO 14.1 | 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://ingage.institute/ | 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).
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://ingage.institute/wp-content/uploads/2018/ | 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 |
| https://ingage.institute/wp-content/uploads/2024/ | 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-03-23 16:40 EET Nmap scan report for ingage.institute (83.166.138.5) Host is up (0.016s latency). Other addresses for ingage.institute (not scanned): 2001:1600:4:13:1a66:daff:fe5c:a597 rDNS record for 83.166.138.5: h2web57.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.23 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 checked 2056 selectors but found no DKIM records.
Vulnerability description
We found that no DKIM record was configured. When a DKIM (DomainKeys Identified Mail) record is not present for a domain, it means that outgoing emails from that domain are not cryptographically signed. DKIM is a critical component of email authentication, allowing recipients to verify that an email was genuinely sent from an authorized server and that the message has not been altered in transit. The absence of a DKIM record leaves the domain vulnerable to email spoofing and phishing attacks, as attackers can send fraudulent emails that appear to originate from the domain without any cryptographic verification.
Risk description
Without a DKIM record, recipients have no way of verifying the integrity or authenticity of emails sent from the domain. This increases the likelihood of phishing and spoofing attacks, where malicious actors impersonate the domain to send fraudulent emails. This can lead to significant security incidents, such as credential theft, financial fraud, or the distribution of malware. Additionally, many email providers use DKIM as part of their spam and reputation filters, meaning that emails from a domain without DKIM may be flagged as spam or rejected, impacting the deliverability and reputation of legitimate emails.
Recommendation
We recommend implementing DKIM for your domain to enhance email security and protect your brand from email-based attacks. Generate a DKIM key pair (public and private keys), publish the public key in the DNS under the appropriate selector, and configure your email servers to sign outgoing messages using the private key. Ensure that the DKIM key length is at least 1024 bits to prevent cryptographic attacks. Regularly monitor DKIM signatures to ensure the system is functioning correctly and update keys periodically to maintain security.
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 |
|---|---|---|---|
| ingage.institute | TXT | Text record | "google-site-verification=VgYhSf3LENCuM5FC1aL_8ofzu0N25wymdAMgvVHlpwU" |
| ingage.institute | TXT | Text record | "sendinblue-site-verification=4254830" |
| ingage.institute | TXT | Text record | "mailerlite-domain-verification=5759990bf0368fcd5af8e6834d7dfe1a68c0bc69" |
Vulnerability description
We found that the target server has no DMARC policy configured. A missing DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy means that the domain is not enforcing any DMARC policies to protect against email spoofing and phishing attacks. Without DMARC, even if SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) are configured, there is no mechanism to tell receiving email servers how to handle messages that fail authentication. This leaves the domain vulnerable to abuse, such as email spoofing and impersonation.
Risk description
Without a DMARC policy, your domain is highly vulnerable to email spoofing, allowing attackers to impersonate your brand and send fraudulent emails that appear legitimate. This can lead to phishing attacks targeting your customers, employees, or partners, potentially resulting in stolen credentials, financial loss, or unauthorized access to sensitive systems. Additionally, repeated spoofing attempts can severely damage your brand's reputation, as recipients may lose trust in communications from your domain, associating your brand with malicious activity. The absence of DMARC also prevents you from monitoring and mitigating email-based attacks, leaving your domain exposed to ongoing abuse.
Recommendation
We recommend implementing a DMARC policy for your domain. Start by configuring a DMARC record with a policy of p=none, which will allow you to monitor email flows without impacting legitimate emails. This initial setup helps identify how emails from your domain are being processed by recipient servers. Once you’ve verified that legitimate emails are passing SPF and DKIM checks, you can gradually enforce stricter policies like p=quarantine or p=reject to protect against spoofing and phishing attacks. Additionally, include rua and ruf email addresses in the DMARC record to receive aggregate and forensic reports. These reports will provide valuable insights into authentication failures and help you detect any spoofing attempts.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| ingage.institute | SPF | Sender Policy Framework | "v=spf1 include:_spf.mlsend.com include:spf.infomaniak.ch ?all" |
Evidence
| Operating System | Accuracy |
|---|---|
| OpenWrt Kamikaze 7.09 (Linux 2.6.22) | 98% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Slider Revolution | Widgets, Photo galleries |
| MySQL | Databases |
| PHP | Programming languages |
| Google Maps | Maps |
| WOW 0.3.6 | JavaScript frameworks, Web frameworks, JavaScript graphics |
| Contact Form 7 5.3.2 | WordPress plugins, Form builders |
| FitVids.JS 1.1.0 | Widgets, Video players |
| Reveal.js | JavaScript frameworks |
| Apache HTTP Server | Web servers |
| WPMU DEV Smush 3.8.2 | WordPress plugins |
| Yoast SEO 14.1 | SEO, WordPress plugins |
| Highlight.js | JavaScript libraries |
| Max Mega Menu 2.9.2 | Widgets, WordPress plugins |
| waitForImages | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| imagesLoaded 3.2.0 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| CookieYes | Cookie compliance |
| HSTS | Security |
| Lodash 1.8.3 | JavaScript libraries |
| wpBakery | Page builders, WordPress plugins |
| Google Font API | Font scripts |
| RSS | Miscellaneous |
| Open Graph | Miscellaneous |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| ingage.institute | A | IPv4 address | 83.166.138.5 |
| ingage.institute | NS | Name server | ns31.infomaniak.com |
| ingage.institute | NS | Name server | ns32.infomaniak.com |
| ingage.institute | MX | Mail server | 5 mta-gw.infomaniak.ch |
| ingage.institute | SOA | Start of Authority | ns31.infomaniak.com. hostmaster.infomaniak.ch. 2026021702 10800 3600 605800 86400 |
| ingage.institute | AAAA | IPv6 address | 2001:1600:4:13:1a66:daff:fe5c:a597 |
| ingage.institute | TXT | Text record | "google-site-verification=VgYhSf3LENCuM5FC1aL_8ofzu0N25wymdAMgvVHlpwU" |
| ingage.institute | TXT | Text record | "sendinblue-site-verification=4254830" |
| ingage.institute | TXT | Text record | "mailerlite-domain-verification=5759990bf0368fcd5af8e6834d7dfe1a68c0bc69" |
| ingage.institute | SPF | Sender Policy Framework | "v=spf1 include:_spf.mlsend.com include:spf.infomaniak.ch ?all" |
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.