Vulnerability Scan Result
| Title: | Home - Parts Cleaning Services - Safetykleen |
| Description: | Safetykleen provides all-in-one parts cleaning services and parts washer hire to customers across the UK and Ireland. |
| ip_address | 141.193.213.21 |
| country | US  |
| network_name | Cloudflare, Inc. |
| asn | AS209242 |
| ip_address | 141.193.213.20 |
| country | US |
| network_name | Cloudflare, Inc. |
| asn | AS209242 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | https | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Microsoft Clarity | Analytics |
| Clipboard.js | JavaScript libraries |
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.20.3 | JavaScript libraries |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.4.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Matomo Analytics | Analytics |
| Material UI | UI frameworks |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OptinMonster | Marketing automation |
| PHP | Programming languages |
| Piwik PRO Core | Analytics |
| React | JavaScript frameworks |
| Social Snowball | Affiliate programs |
| styled-components 6.1.19 | JavaScript frameworks, Development |
| DoubleClick Floodlight | Advertising |
| Google Call Conversion Tracking | Analytics |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| WP Engine | PaaS, Hosting |
| WPML 4.9.4 | WordPress plugins, Translation |
| Cookie Control | Cookie compliance |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| Cookiebot 1 | Cookie compliance |
| Cybot | Cookie compliance |
| Formstack | Form builders |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| LiveChat | Live chat |
| Lodash 1.13.8 | JavaScript libraries |
| HSTS | Security |
| StackAdapt | Advertising |
| Webeo | Personalisation |
| Yoast SEO 27.8 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.8383 | 0.99653 | 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.99019 | 0.99925 | In jQuery starting with 1.12.0 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. |
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://safetykleeninternational.com/ | geo_country | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: geo_country=DE |
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://safetykleeninternational.com/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Microsoft Clarity | Analytics |
| Clipboard.js | JavaScript libraries |
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.20.3 | JavaScript libraries |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.4.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Matomo Analytics | Analytics |
| Material UI | UI frameworks |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OptinMonster | Marketing automation |
| PHP | Programming languages |
| Piwik PRO Core | Analytics |
| React | JavaScript frameworks |
| Social Snowball | Affiliate programs |
| styled-components 6.1.19 | JavaScript frameworks, Development |
| DoubleClick Floodlight | Advertising |
| Google Call Conversion Tracking | Analytics |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| WP Engine | PaaS, Hosting |
| WPML 4.9.4 | WordPress plugins, Translation |
| Cookie Control | Cookie compliance |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| Cookiebot 1 | Cookie compliance |
| Cybot | Cookie compliance |
| Formstack | Form builders |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| LiveChat | Live chat |
| Lodash 1.13.8 | JavaScript libraries |
| HSTS | Security |
| StackAdapt | Advertising |
| Webeo | Personalisation |
| Yoast SEO 27.8 | 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://safetykleeninternational.com/wp-json/oembed/1.0/embed | GET | Query: format=xml url=https://safetykleeninternational.com/ 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: __cf_bm=EDlNTbYXJZ39hguvvuIw1mIL9Gcg8.Gd4KLle7cAzwQ-1782226370.597325-1.0.1... | Possible API endpoint found at |
| https://safetykleeninternational.com/wp-json/oembed/1.0/embed | GET | Query: url=https://safetykleeninternational.com/ 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: __cf_bm=EDlNTbYXJZ39hguvvuIw1mIL9Gcg8.Gd4KLle7cAzwQ-1782226370.597325-1.0.1.1-qh8mkVsD... | 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 |
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.8383 | 0.99653 | Yes | 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.99019 | 0.99925 | No | In jQuery starting with 1.12.0 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. |
Vulnerability description
Vulnerabilities found for jQuery 3.4.1
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.8383 | 0.99653 | Yes | 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.99019 | 0.99925 | No | In jQuery starting with 1.12.0 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. |
Vulnerability description
Vulnerabilities found for jQuery 3.4.1
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.safetykleeninternational.com | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:0d97cf81bae1775@rep.dmarcanalyzer.com; ruf=mailto:0d97cf81bae1775@for.dmarcanalyzer.com; fo=1;" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns23.domaincontrol.com, ns24.domaincontrol.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| safetykleeninternational.com | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| styled-components 6.1.19 | JavaScript frameworks, Development |
| MySQL | Databases |
| PHP | Programming languages |
| Material UI | UI frameworks |
| Formstack | Form builders |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Yoast SEO 27.8 | SEO, WordPress plugins |
| Google Font API | Font scripts |
| WPML 4.9.4 | WordPress plugins, Translation |
| StackAdapt | Advertising |
| Social Snowball | Affiliate programs |
| MailChimp | Marketing automation, Email |
| Linkedin Ads | Advertising |
| Google Hosted Libraries | CDN |
| Cloudflare Bot Management | Security |
| Amazon S3 | CDN |
| Twitter Emoji (Twemoji) | Font scripts |
| OptinMonster | Marketing automation |
| Microsoft Clarity | Analytics |
| Microsoft Advertising | Advertising |
| LiveChat | Live chat |
| jQuery 3.4.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Call Conversion Tracking | Analytics |
| Google Analytics | Analytics |
| core-js 3.20.3 | JavaScript libraries |
| Cookiebot 1 | Cookie compliance |
| Cookie Control | Cookie compliance |
| Webeo | Personalisation |
| Cybot | Cookie compliance |
| Piwik PRO Core | Analytics |
| reCAPTCHA | Security |
| Linkedin Insight Tag | Analytics |
| DoubleClick Floodlight | Advertising |
| WP Engine | PaaS, Hosting |
| HSTS | Security |
| Cloudflare | CDN |
| PWA | Miscellaneous |
| Open Graph | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Clipboard.js | JavaScript libraries |
| Lodash 1.13.8 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Matomo Analytics | Analytics |
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 |
|---|---|---|---|
| safetykleeninternational.com | A | IPv4 address | 141.193.213.20 |
| safetykleeninternational.com | A | IPv4 address | 141.193.213.21 |
| safetykleeninternational.com | NS | Name server | ns23.domaincontrol.com |
| safetykleeninternational.com | NS | Name server | ns24.domaincontrol.com |
| safetykleeninternational.com | MX | Mail server | 0 safetykleeninternational-com.mail.protection.outlook.com |
| safetykleeninternational.com | SOA | Start of Authority | ns23.domaincontrol.com. dns.jomax.net. 2026060301 28800 7200 604800 600 |
| safetykleeninternational.com | TXT | Text record | "facebook-domain-verification=944boeitqp40ce4yowlaqv59gcov5j" |
| safetykleeninternational.com | TXT | Text record | "google-site-verification=l0dO1wMQhJD5fH9VtqxBRjm46u9-yxn1qyRL-d47Xug" |
| safetykleeninternational.com | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |
| _dmarc.safetykleeninternational.com | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:0d97cf81bae1775@rep.dmarcanalyzer.com; ruf=mailto:0d97cf81bae1775@for.dmarcanalyzer.com; fo=1;" |
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| s2 | rsa | 1296 | "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDUWUwba47CwgSVw5DBma8LMc3Z4hmJK7kBMYtuMrIvuOJ4DHW3VfzHhfMQo1lIQVy3R2Q3WILeHwx2C3NNhhlrUEjU5kxQvXmPS6JgZbR5sTzZpgNFAwyKd3KDzNXZl5tQo4q5Jxt7QF1eEWH1vp5E1M/OauIaqU/RMtS/7EjryQIDAQAB" |
| s1 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6pQaSMs1YnR8j/yzGe+OK8zO0mr9euLniBJPF/7OCKXKChq3YOeA34pzPvXpVfurMBnlvfDUkwyrdHyI+yENgQjIjvX0M5juY6m6qzNZQx187YGSvhWm5ptSBOYgB0qB5nvDM8vnfWw4rznrqbCMNBJo8VGPjpZZcS6OmkH6KhDvw3V4aXoCkb2N/4u7eam/6eRHR" "KS0HfIUH0uCpHdiLGB1zjtTXswrIAXl0sM/9WUs2P2R6Yw0bAwFDRvPv3E90EQjnRLseXHsSSw9fNkoNvbHcP3MJYECpAITjSKAJoV3YdPp1spxIYi4pqYx8D9DGR9JkDtRXvx0khhcogechwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| styled-components 6.1.19 | JavaScript frameworks, Development |
| MySQL | Databases |
| PHP | Programming languages |
| Material UI | UI frameworks |
| Formstack | Form builders |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Yoast SEO 27.8 | SEO, WordPress plugins |
| Google Font API | Font scripts |
| WPML 4.9.4 | WordPress plugins, Translation |
| StackAdapt | Advertising |
| Social Snowball | Affiliate programs |
| MailChimp | Marketing automation, Email |
| Linkedin Ads | Advertising |
| Google Hosted Libraries | CDN |
| Cloudflare Bot Management | Security |
| Amazon S3 | CDN |
| Twitter Emoji (Twemoji) | Font scripts |
| OptinMonster | Marketing automation |
| Microsoft Clarity | Analytics |
| Microsoft Advertising | Advertising |
| LiveChat | Live chat |
| jQuery 3.4.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Call Conversion Tracking | Analytics |
| Google Analytics | Analytics |
| core-js 3.20.3 | JavaScript libraries |
| Cookiebot 1 | Cookie compliance |
| Cookie Control | Cookie compliance |
| Webeo | Personalisation |
| Cybot | Cookie compliance |
| reCAPTCHA | Security |
| Piwik PRO Core | Analytics |
| Linkedin Insight Tag | Analytics |
| DoubleClick Floodlight | Advertising |
| WP Engine | PaaS, Hosting |
| HSTS | Security |
| Cloudflare | CDN |
| PWA | Miscellaneous |
| Open Graph | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Underscore.js 1.13.8 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
| Matomo Analytics | Analytics |
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.