Vulnerability Scan Result

Target:

https://www.dockjeanssale.shop/

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

Submitted: May 22, 2025 from DE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	ㅤㅤㅤ
Description:	ㅤㅤㅤ

IP Information

IP address	104.18.3.225
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
HTTP/3	Miscellaneous
PHP	Programming languages
Stripe	Payment processors
Vue.js	JavaScript frameworks
Cloudflare	CDN
Cloudflare Bot Management	Security
TinyMCE	Rich text editors

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.dockjeanssale.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.1747924396566.5816058728 Set-Cookie: _auth_debug=wyxx5x47rmq8ul93aM%2FULuanjonXEImYV87aU%2Fw7FC4f8lETcplWaXt79lPPPDDEBbwvIMkMEKUrhOOXU7DcZmq1gjBahnBGh3UZfQ%3D%3D Set-Cookie: shop_global_visit_id=558B9EA2-9F45-20F6-882D-970A9396E23D Set-Cookie: shop_checkout_visit_id=E9DDD690-D368-D9BE-0BFF-D7F821EFBDA1 Set-Cookie: shop_global_visit_session=7ED4615D-F820-206F-59B8-2BE7982D2788

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	Cookie Name	Evidence
https://www.dockjeanssale.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.1747924396566.5816058728 Set-Cookie: _auth_debug=wyxx5x47rmq8ul93aM%2FULuanjonXEImYV87aU%2Fw7FC4f8lETcplWaXt79lPPPDDEBbwvIMkMEKUrhOOXU7DcZmq1gjBahnBGh3UZfQ%3D%3D Set-Cookie: shop_global_visit_id=558B9EA2-9F45-20F6-882D-970A9396E23D Set-Cookie: shop_checkout_visit_id=E9DDD690-D368-D9BE-0BFF-D7F821EFBDA1 Set-Cookie: shop_global_visit_session=7ED4615D-F820-206F-59B8-2BE7982D2788 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%3A1747924396%2C%22expire_time%22%3A1750516396%7D%5D Set-Cookie: landing_page=aHR0cHM6Ly93d3cuZG9ja2plYW5zc2FsZS5zaG9wLw%3D%3D Set-Cookie: shop_keep_alive=860E154E-0208-A09C-D7FB-00FC322AEFBE Set-Cookie: first_http_referer=null Set-Cookie: first_visit_time=1747924396 Set-Cookie: PHPSESSID=ec37717fcdbc8b613f31155963837e41

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

Software / Version	Category
HTTP/3	Miscellaneous
PHP	Programming languages
Stripe	Payment processors
Vue.js	JavaScript frameworks
Cloudflare	CDN
Cloudflare Bot Management	Security
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
https://www.dockjeanssale.shop/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).

Classification

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

Evidence

URL	Method	Parameters	Evidence
https://www.dockjeanssale.shop/pages/Contact-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: PHPSESSID=a481adc5c65b03f75d635f42c7f3b65f __cf_bm=HDy2.LVYx0jRpKQIcbU3rEN3Y8NfX9._MgZu0PWEK0o-1747924400-1.0.1.1-XXvfIxr_UOY.5.Z9.Lt.3WkC.cgO...	Email Address: support@nnrroo.shop

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
Missing: https://www.dockjeanssale.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.dockjeanssale.shop	A	IPv4 address	104.18.3.225

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.0-RELEASE	91%

Evidence

Software / Version	Category
TinyMCE	Rich text editors
PHP	Programming languages
Vue.js	JavaScript frameworks
Stripe	Payment processors
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
TinyMCE	Rich text editors
PHP	Programming languages
Vue.js	JavaScript frameworks
Stripe	Payment processors
Cloudflare	CDN
HTTP/3	Miscellaneous
Cloudflare Bot Management	Security

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.