Vulnerability Scan Result

Target:

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

Scanned target: https://moobrew.com.au/

Submitted: Jun 09, 2026 from FM

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Moo Brew – Moo Brew Brewery
Description:	Our brewery makes seven beers year-round, plus one or two seasonals and limited releases here and there. No preservatives. No additives.

IP Information

ip_address	23.227.38.65
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
Facebook Pixel 2.9.338	Analytics
core-js 2.6.12	JavaScript libraries
Glide.js	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Open Graph	Miscellaneous
PayPal	Payment processors
PHP	Programming languages
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Priority Hints	Performance
WordPress	CMS, Blogs
ActiveCampaign	Marketing automation, Email
Apple Pay	Payment processors
Cloudflare	CDN
Google Tag Manager	Tag managers
HSTS	Security
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://moobrew.com.au/	localization, cart_currency, _shopify_y, _shopify_s	Set-Cookie: localization=AU Set-Cookie: cart_currency=AUD Set-Cookie: _shopify_y=a5f12289-6849-4273-a3c1-6b43a509670c Set-Cookie: _shopify_s=1dbb0bc5-48aa-41a9-94d2-639dac77373a

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://moobrew.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=a5f12289-6849-4273-a3c1-6b43a509670c Set-Cookie: _shopify_s=1dbb0bc5-48aa-41a9-94d2-639dac77373a

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://moobrew.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
Facebook Pixel 2.9.338	Analytics
core-js 2.6.12	JavaScript libraries
Glide.js	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Open Graph	Miscellaneous
PayPal	Payment processors
PHP	Programming languages
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Priority Hints	Performance
WordPress	CMS, Blogs
ActiveCampaign	Marketing automation, Email
Apple Pay	Payment processors
Cloudflare	CDN
Google Tag Manager	Tag managers
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	Method	Parameters	Evidence
https://moobrew.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	Suspicious comment admin found in: `ause it is already included via the Shopify admin and shouldn't be loaded twice. https://moo-`

Vulnerability description

We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.

Risk description

The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.

Recommendation

Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.

Classification

CWE	CWE-546
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://moobrew.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'. 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. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.`

https://moobrew.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'. 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. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.

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
https://moobrew.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
Missing: https://moobrew.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://moobrew.com.au/pages/contact	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=:AZ7aeA1RAAEAzNp816xnvrPXIY2Zfphr6zh1BjP7JpWjfEPxr6XZ0ELPJpu5B275BGbeS3IlZgPPwOpuzQIHC6aGq2V4rWtY22Oeh6E: _shopify_essentia...	Email Address: tassales@moobrew.com.au beer@moobrew.com.au info@moobrew.com.au media@mona.net.au
https://moobrew.com.au/pages/manky-sallys	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=:AZ7aeA1RAAEAzNp816xnvrPXIY2Zfphr6zh1BjP7JpWjfEPxr6XZ0ELPJpu5B275BGbeS3IlZgPPwOpuzQIHC6aGq2V4rWtY22Oeh6E: _shopify_essentia...	Email Address: sallys@moobrew.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

Domain Queried	DNS Record Type	Description	Value
_dmarc.moobrew.com.au	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:dmarc@mona.net.au; ruf=mailto:dmarc@mona.net.au; adkim=s; aspf=s; 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

Domain Queried	DNS Record Type	Description	Value
moobrew.com.au	SPF	Sender Policy Framework	"v=spf1 include:_spf.google.com include:mailgun.org include:sendgrid.net ip4:120.151.109.103 ~all"

Vulnerability description

We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.

Risk description

The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.

Recommendation

We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.

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-STABLE	91%

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

Domain Queried	DNS Record Type	Description	Value
moobrew.com.au	A	IPv4 address	23.227.38.65
moobrew.com.au	NS	Name server	ns-1352.awsdns-41.org
moobrew.com.au	NS	Name server	ns-1777.awsdns-30.co.uk
moobrew.com.au	NS	Name server	ns-460.awsdns-57.com
moobrew.com.au	NS	Name server	ns-552.awsdns-05.net
moobrew.com.au	MX	Mail server	1 aspmx.l.google.com
moobrew.com.au	MX	Mail server	10 alt3.aspmx.l.google.com
moobrew.com.au	MX	Mail server	10 alt4.aspmx.l.google.com
moobrew.com.au	MX	Mail server	5 alt1.aspmx.l.google.com
moobrew.com.au	MX	Mail server	5 alt2.aspmx.l.google.com
moobrew.com.au	SOA	Start of Authority	ns-460.awsdns-57.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
moobrew.com.au	TXT	Text record	"1password-site-verification=SLQMS7WOSFBIJGKNDXJ24N34JA"
moobrew.com.au	TXT	Text record	"google-site-verification=7pdfNy8n5xtak1FhRcWx9WD3qhRon71sZiBoItebPDw"
moobrew.com.au	SPF	Sender Policy Framework	"v=spf1 include:_spf.google.com include:mailgun.org include:sendgrid.net ip4:120.151.109.103 ~all"
_dmarc.moobrew.com.au	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:dmarc@mona.net.au; ruf=mailto:dmarc@mona.net.au; adkim=s; aspf=s; 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

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
Shopify	Ecommerce
Cart Functionality	Ecommerce
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Shop Pay	Payment processors
Apple Pay	Payment processors
PayPal	Payment processors
Glide.js	JavaScript libraries
core-js 2.6.12	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Facebook Pixel 2.9.338	Analytics
ActiveCampaign	Marketing automation, Email
Priority Hints	Performance
DoubleClick Floodlight	Advertising
HSTS	Security
Cloudflare	CDN
Open Graph	Miscellaneous
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

DKIM selector	Key type	Key size	Value
google	rsa	1296	"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCMWX9PxgErQTr3etLbtqCrAZx864T6njRxImWgCW/+/zfm4nw6D+mNkVdwHNCw+q2wr74saWOE0Ad3S3HUVfQnRr4jZ+kBTjCANVDIDncfuB5y7ppzgN/KODJnIrKiVB+saf8JhqZCWr/rw4n+1Y9yHWi7S8bOhAMyJ78P/+dLmwIDAQAB"
mx	rsa	1296	"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDDuN4MufiqSen3o6iniWdt7US/SfkmZ0gzL/voC7vMJIikSlV/6VxbSxXm2lWQPwWZMvHHiwu+OZDnUZ6c1EmwB5p2VnxAIejimpctP/X2X456O5O1+m4LSIC5vLg5OxI3nBItIj7dpL4LMyqZ8NV7x1p+U9DL+GhxtWWZ0nzY1QIDAQAB"
s2	rsa	1296	"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDojwYASi4zrvP1Py6Ha+Xrd0dteuXvsWon37E879gHTjMP4+K2a+Td9Vfh7ADyu9kcZHdmLExPpn5oMScywRoSw5fk79o5vQWyPhoR+PUEBsj3BAacdRBKCbjVvXtKvImOO1DUvtqqRHac968cFxer64tXdoS7RIqGA0xecmmCgwIDAQAB"
s1	rsa	1446	"k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0NxJpItAPDa2GHjcnuUYQJS+kebSuXynoPC65TIO3i/RIIk1JyWNsSIP8ocpK7d+hFe5MWxuXLXKvWdkSUNVRntevy71GMMi++etpcg0QJAbQOSHwFzV8iDOxQlX0u/WsCMwRgk6BBPl6n0pXa86wXGZsi9znVCzBoLhHOsqnev2EOKfq82MTaW16k8LK7GjRliAs" "k/A+xC/8OjVQ8YVvz636mSVzaViRGbvKaUVQs6GYwft+Q6jn7U+C2gDzd+cxetGN1wEt5iaob3npLkALZmT30oGmUsGydAelP2RktETwvJElVvwLJDikIVFd9ReiqOdeRJLT0CfaCLqjCvSVQIDAQAB"