Vulnerability Scan Result

Target:

http://panfan.com.au/ (redirect)

Scanned target: https://www.panfan.com.au/

Submitted: May 04, 2026 from GD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Pan Fan Australia \| Panfan - Never Have A Smelly Bathroom Again!
Description:	Total bathroom odour removal system! Panfan creates a much more hygienic, odour-free bathroom. Panfan filters the air drawn from the bowl with an active-carbon filter or vented directly outside; eliminating unwanted smell and 99.9% of harmful micro-organisms that would otherwise be released into your bathroom.

IP Information

ip_address	23.227.38.74
country	CA
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

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 -

Web Technologies

Software / Version	Category
Google Ads	Advertising
Globo Form Builder	Shopify apps, Form builders
Amazon Web Services	PaaS
bxSlider	Photo galleries, JavaScript libraries
Google Hosted Libraries	CDN
Facebook Pixel 2.9.313	Analytics
Flickity 2	JavaScript libraries
Font Awesome	Font scripts
Adobe Fonts	Font scripts
core-js 3.37.0	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
jQuery 1.10.0	JavaScript libraries
MailChimp	Marketing automation, Email
Modernizr 2.7.1	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PayPal	Payment processors
PHP	Programming languages
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Google Ads Conversion Tracking	Analytics
Typekit	Font scripts
Unpkg	CDN
Priority Hints	Performance
WordPress	CMS, Blogs
Afterpay	Payment processors, Buy now pay later
Apple Pay	Payment processors
Cloudflare	CDN
WOW	JavaScript frameworks, Web frameworks, JavaScript graphics
Google Tag Manager	Tag managers
Hotjar	Analytics
Klaviyo	Marketing automation
Klaviyo Reviews	Reviews
HSTS	Security
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2020-11023	6.9	0.66129	0.98535	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.07042	0.91527	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.
CVE-2019-11358	6.1	0.02426	0.85206	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.96407	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	Cookie Name	Evidence
https://www.panfan.com.au/	localization, cart_currency, _shopify_y, _shopify_s	Set-Cookie: localization=AU Set-Cookie: cart_currency=AUD Set-Cookie: _shopify_y=8118f9e0-a896-4c32-a574-94e34a3584df Set-Cookie: _shopify_s=d1f44dc4-fd99-4d8f-85cc-bdfa4baeb114

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://www.panfan.com.au/	localization, cart_currency, _shopify_y, _shopify_s	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: localization=AU Set-Cookie: cart_currency=AUD Set-Cookie: _shopify_y=8118f9e0-a896-4c32-a574-94e34a3584df Set-Cookie: _shopify_s=d1f44dc4-fd99-4d8f-85cc-bdfa4baeb114

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

URL	Evidence
https://www.panfan.com.au/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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

Software / Version	Category
Google Ads	Advertising
Globo Form Builder	Shopify apps, Form builders
Amazon Web Services	PaaS
bxSlider	Photo galleries, JavaScript libraries
Google Hosted Libraries	CDN
Facebook Pixel 2.9.313	Analytics
Flickity 2	JavaScript libraries
Font Awesome	Font scripts
Adobe Fonts	Font scripts
core-js 3.37.0	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
jQuery 1.10.0	JavaScript libraries
MailChimp	Marketing automation, Email
Modernizr 2.7.1	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PayPal	Payment processors
PHP	Programming languages
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Google Ads Conversion Tracking	Analytics
Typekit	Font scripts
Unpkg	CDN
Priority Hints	Performance
WordPress	CMS, Blogs
Afterpay	Payment processors, Buy now pay later
Apple Pay	Payment processors
Cloudflare	CDN
WOW	JavaScript frameworks, Web frameworks, JavaScript graphics
Google Tag Manager	Tag managers
Hotjar	Analytics
Klaviyo	Marketing automation
Klaviyo Reviews	Reviews
HSTS	Security
Cart Functionality	Ecommerce

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
https://www.panfan.com.au/robots.txt

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.panfan.com.au/	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	Different hostname found for a source file `shopify`
https://www.panfan.com.au/pages/about-us	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: _shopify_analytics=:AZ3wX-EFAAEAHhISTQQYPZJoKGsUVqh6f8K4gRkh7lbc3l8fZlEtKrThLKxdnEoCPqcMmUSSmEYm2UruMC37BEBo2Jmqm0G6PEoApi5clokB3-1BeX1vp9t_fx...	Different hostname found for a source file `shopify`

Vulnerability description

We have noticed that the target application includes scripts from external domains. This may be problematic as such scripts have the same level of access as the application's own scripts, which means they can interact with application data and perform actions as the current user.

Risk description

The risk is that cross domain file inclusion can lead to a wide variety security breaches if the external scripts are malicious or become compromised.

Recommendation

You do not have any control over what is in that code. Ensure files on the site are loaded from only trusted sources.

Classification

CWE	CWE-829
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://www.panfan.com.au/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing.`

https://www.panfan.com.au/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing.

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

URL
Missing: https://www.panfan.com.au/.well-known/security.txt

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.panfan.com.au/products/vented-fan-kit-pfv	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: _shopify_analytics=:AZ3wX-EFAAEAHhISTQQYPZJoKGsUVqh6f8K4gRkh7lbc3l8fZlEtKrThLKxdnEoCPqcMmUSSmEYm2UruMC37BEBo2Jmqm0G6PEoApi5clokB3-1BeX1vp9t_fx...	Email Address: 20sales@panfan.com.au u003esales@panfan.com.au

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-2020-11023	6.9	0.66129	0.98535	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.07042	0.91527	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.
CVE-2019-11358	6.1	0.02426	0.85206	No	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.96407	No	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

Vulnerabilities found for jQuery 1.10.0

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 that jQuery has reached the End-of-Life (EOL).

Version detected: 1.10.0 Latest version for the cycle: 1.12.4 This release cycle (1) doesn't have long-term-support (LTS). The cycle was released on 2006-08-31 and its latest release date was 2016-05-20.

Risk description

Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.

Recommendation

To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.

Evidence

Software / Version	Category
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	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	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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
Shopify	Ecommerce
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
WOW	JavaScript frameworks, Web frameworks, JavaScript graphics
YouTube	Video players
Globo Form Builder	Shopify apps, Form builders
Amazon Web Services	PaaS
PayPal	Payment processors
Google Ads	Advertising
Unpkg	CDN
Typekit	Font scripts
Modernizr	JavaScript libraries
MailChimp	Marketing automation, Email
Klaviyo	Marketing automation
jQuery 1.10.0	JavaScript libraries
Hotjar	Analytics
Google Tag Manager	Tag managers
Google Hosted Libraries	CDN
Google Analytics GA4	Analytics
Google Ads Conversion Tracking	Analytics
Font Awesome	Font scripts
Flickity 2	JavaScript libraries
Facebook Pixel 2.9.313	Analytics
bxSlider	Photo galleries, JavaScript libraries
Adobe Fonts	Font scripts
DoubleClick Floodlight	Advertising
HSTS	Security
Cloudflare	CDN
HTTP/3	Miscellaneous
Afterpay	Payment processors, Buy now pay later

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
www.panfan.com.au	A	IPv4 address	23.227.38.74
www.panfan.com.au	AAAA	IPv6 address	2620:127:f00f:e::
www.panfan.com.au	CAA	Certificate Authority Authorization	0 issue "digicert.com"
www.panfan.com.au	CAA	Certificate Authority Authorization	0 issue "globalsign.com"
www.panfan.com.au	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
www.panfan.com.au	CAA	Certificate Authority Authorization	0 issue "pki.goog"
www.panfan.com.au	CAA	Certificate Authority Authorization	0 issue "ssl.com"
www.panfan.com.au	CNAME	Canonical name	shops.myshopify.com

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
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	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	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.