Vulnerability Scan Result

Target:

https://www.diggsa.shop/

Scanned target: https://www.diggsa.shop/

Submitted: May 22, 2025 from CG

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	vivalavidaa.shop
Description:	vivalavidaa

IP Information

IP address	172.67.130.158
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.8.200
Country	-
AS number	AS13335
Net name	Cloudflare Inc

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
PHP	Programming languages
Stripe	Payment processors
Vue.js	JavaScript frameworks
Cloudflare	CDN
TinyMCE	Rich text editors

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.diggsa.shop/	_fbs_fbp, _auth_debug, shop_global_visit_id, shop_checkout_visit_id, shop_global_visit_session, utm_source, utm_medium, order_utm_history, landing_page, shop_keep_alive, first_http_referer, first_visit_time, PHPSESSID	Set-Cookie: _fbs_fbp=fb.1.1747952474733.9434665670 Set-Cookie: _auth_debug=8wz0f6lb4sj7ltgtii4dBIPV9VUICX6z96vo6R0vVri%2Fr7UnEMjrx0yefSCFQDcUzpDA8%2FLdOviJHUg9WnwTe17VxjUuIZhchECSMQ%3D%3D Set-Cookie: shop_global_visit_id=2BA23D8E-725B-B88A-51B4-B3205F879BC4 Set-Cookie: shop_checkout_visit_id=0C4A50E7-1E58-AD55-E7E7-E807FC69587C Set-Cookie: shop_global_visit_session=70E168E4-AFDC-CFA3-B55E-A1384CF48DAB Set-Cookie: utm_source=direct Set-Cookie: utm_medium=default Set-Cookie: order_utm_history=%5B%7B%22utm_source%22%3A%22direct%22%2C%22utm_medium%22%3A%22default%22%2C%22utm_term%22%3A%22%22%2C%22utm_campaign%22%3A%22%22%2C%22utm_content%22%3A%22%22%2C%22source_device%22%3A%22computer%22%2C%22create_time%22%3A1747952474%2C%22expire_time%22%3A1750544474%7D%5D Set-Cookie: landing_page=aHR0cHM6Ly93d3cuZGlnZ3NhLnNob3Av Set-Cookie: shop_keep_alive=3D14A3C2-775D-EEFA-3563-733D01C374F6 Set-Cookie: first_http_referer=null Set-Cookie: first_visit_time=1747952474 Set-Cookie: PHPSESSID=e2399b048a430a4a19e5cf66f53cafe6

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Cookie Name	Evidence
https://www.diggsa.shop/	_fbs_fbp, _auth_debug, shop_global_visit_id, shop_checkout_visit_id, shop_global_visit_session	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: _fbs_fbp=fb.1.1747952474733.9434665670 Set-Cookie: _auth_debug=8wz0f6lb4sj7ltgtii4dBIPV9VUICX6z96vo6R0vVri%2Fr7UnEMjrx0yefSCFQDcUzpDA8%2FLdOviJHUg9WnwTe17VxjUuIZhchECSMQ%3D%3D Set-Cookie: shop_global_visit_id=2BA23D8E-725B-B88A-51B4-B3205F879BC4 Set-Cookie: shop_checkout_visit_id=0C4A50E7-1E58-AD55-E7E7-E807FC69587C Set-Cookie: shop_global_visit_session=70E168E4-AFDC-CFA3-B55E-A1384CF48DAB

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://www.diggsa.shop/	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

CWE	CWE-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://www.diggsa.shop/	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-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://www.diggsa.shop/	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Method	Parameters	Evidence
https://www.diggsa.shop/account/login	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	The following form sends inputs of type password plainly in the URL: ` Email Password CONFIRM Reset Password Create Account <div class="plugin-con... (truncated)

Vulnerability description

We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.

Risk description

Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.

Recommendation

You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.

Classification

OWASP Top 10 - 2017
OWASP Top 10 - 2021	A4 - Insecure Design

Evidence

Software / Version	Category
PHP	Programming languages
Stripe	Payment processors
Vue.js	JavaScript frameworks
Cloudflare	CDN
TinyMCE	Rich text editors

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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Method	Parameters	Evidence
https://www.diggsa.shop/	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	Email Address: help@vivalavidaa.site

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	A6: Security Misconfiguration
OWASP Top 10 - 2021	A4: Insecure Design

Evidence

URL Evidence

URL	Evidence
https://www.diggsa.shop/account/login	<input autocomplete="new-password" class="mo-form-input" id="email" name="email" placeholder="Email" type="text" value=""/> <input autocomplete="new-password" class="mo-form-input" id="password" name="password" placeholder="Password" type="password" value=""/> <button class="bg-transparent" type="submit"> <svg class="-rotate-90" height="25" viewbox="0 0 32 32" width="25" xmlns="http://www.w3.org/2000/svg"> <path d="M 19 3 C 13.488281 3 9 7.488281 9 13 C 9 15.394531 9.839844 17.589844 11.25 19.3125 L 3.28125 27.28125 L 4.71875 28.71875 L 12.6875 20.75 C 14.410156 22.160156 16.605469 23 19 23 C 24.511719 23 29 18.511719 29 13 C 29 7.488281 24.511719 3 19 3 Z M 19 5 C 23.429688 5 27 8.570313 27 13 C 27 17.429688 23.429688 21 19 21 C 14.570313 21 11 17.429688 11 13 C 11 8.570313 14.570313 5 19 5 Z" fill="#ffffff"></path> </svg> </button>

https://www.diggsa.shop/account/login

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Evidence

URL
Missing: https://www.diggsa.shop/.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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.diggsa.shop	A	IPv4 address	104.21.8.200
www.diggsa.shop	A	IPv4 address	172.67.130.158
www.diggsa.shop	AAAA	IPv6 address	2606:4700:3035::ac43:829e
www.diggsa.shop	AAAA	IPv6 address	2606:4700:3036::6815:8c8

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.

Operating System	Accuracy
FreeBSD 11.1-STABLE	91%

Evidence

Software / Version	Category
PHP	Programming languages
Cloudflare	CDN

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
PHP	Programming languages
Cloudflare	CDN

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

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.