Vulnerability Scan Result

Target:

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

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

Submitted: Jun 19, 2026 from CH

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Furry 'n' Fabulous Pet Boutique: Treat Your Dog.
Description:	Your premier dog pet product shop with a large selection of high-quality dog harnesses, cat leads, puppy leashes, dog bowls, puppy toys and treats, natural dog food, vegetarian dog treats, dog travel accessories, biodegradable poop bags, pet bedding, dog fashion and more. Shop online anytime for delivery & pickup

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
Babel	Miscellaneous
BugSnag	Analytics, Issue trackers
Facebook Pixel 2.9.349	Analytics
LazySizes	JavaScript libraries, Performance
core-js 2.6.12	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
Judge.me	Reviews
MySQL	Databases
Open Graph	Miscellaneous
PayPal	Payment processors
PHP	Programming languages
Piwik PRO Core	Analytics
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Priority Hints	Performance
WordPress	CMS, Blogs
Afterpay	Payment processors, Buy now pay later
Apple Pay	Payment processors
Cloudflare	CDN
Google Tag Manager	Tag managers
HSTS	Security
Yotpo Loyalty & Referrals	Loyalty & rewards
Yotpo Reviews	Reviews

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.furryandfabulous.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=6a007c46-b7a4-4b20-96e6-9215642a9bd0 Set-Cookie: _shopify_s=74c3d1ca-72e8-4273-b4eb-90bed5f25683

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	Cookie Name	Evidence
https://www.furryandfabulous.com.au/	localization, cart_currency, _shopify_y, _shopify_s	Set-Cookie: localization=AU Set-Cookie: cart_currency=AUD Set-Cookie: _shopify_y=6a007c46-b7a4-4b20-96e6-9215642a9bd0 Set-Cookie: _shopify_s=74c3d1ca-72e8-4273-b4eb-90bed5f25683

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	Evidence
https://www.furryandfabulous.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

URL Evidence

URL	Evidence
https://www.furryandfabulous.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. script-src: script-src directive is missing. 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'.`

https://www.furryandfabulous.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. script-src: script-src directive is missing. 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'.

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	Evidence
https://www.furryandfabulous.com.au/contact	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

Software / Version	Category
Babel	Miscellaneous
BugSnag	Analytics, Issue trackers
Facebook Pixel 2.9.349	Analytics
LazySizes	JavaScript libraries, Performance
core-js 2.6.12	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
Judge.me	Reviews
MySQL	Databases
Open Graph	Miscellaneous
PayPal	Payment processors
PHP	Programming languages
Piwik PRO Core	Analytics
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Priority Hints	Performance
WordPress	CMS, Blogs
Afterpay	Payment processors, Buy now pay later
Apple Pay	Payment processors
Cloudflare	CDN
Google Tag Manager	Tag managers
HSTS	Security
Yotpo Loyalty & Referrals	Loyalty & rewards
Yotpo Reviews	Reviews

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://www.furryandfabulous.com.au/contact	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Shopify	Ecommerce
WordPress	CMS, Blogs
BugSnag	Analytics, Issue trackers
MySQL	Databases
PHP	Programming languages
PayPal	Payment processors
Apple Pay	Payment processors
Shop Pay	Payment processors
Priority Hints	Performance
Afterpay	Payment processors, Buy now pay later
Yotpo Reviews	Reviews
Yotpo Loyalty & Referrals	Loyalty & rewards
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Facebook Pixel 2.9.349	Analytics
DoubleClick Floodlight	Advertising
Piwik PRO Core	Analytics
HSTS	Security
Cloudflare	CDN
Open Graph	Miscellaneous
HTTP/3	Miscellaneous
core-js 3.37.0	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.

Operating System	Accuracy
FreeBSD 11.0-STABLE	91%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.furryandfabulous.com.au	A	IPv4 address	23.227.38.74
www.furryandfabulous.com.au	AAAA	IPv6 address	2620:127:f00f:e::
www.furryandfabulous.com.au	CAA	Certificate Authority Authorization	0 issue "digicert.com"
www.furryandfabulous.com.au	CAA	Certificate Authority Authorization	0 issue "globalsign.com"
www.furryandfabulous.com.au	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
www.furryandfabulous.com.au	CAA	Certificate Authority Authorization	0 issue "pki.goog"
www.furryandfabulous.com.au	CAA	Certificate Authority Authorization	0 issue "ssl.com"
www.furryandfabulous.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.

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.