Vulnerability Scan Result

Target:

http://capt77quantum.com/ (redirect)

Scanned target: https://capt77quantum.com/

Submitted: Dec 03, 2025 from KW

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:

Captain77 â Legend Nexus â Portal Utama Menuju Era Baru 2025 â Captain77

Description:

Captain77 mempersembahkan Legend Nexus, sebuah ruang digital bergaya futuristik yang dirancang untuk mengubah cara pengguna menjelajahi pengalaman online di tahun 2025. Dengan identitas baru yang lebih dinamis, visual yang lebih ekspresif, dan ekosistem interaktif yang mendukung eksplorasi tak terbatas, Legend Nexus menghadirkan nuansa modern yang membawa pengguna ke babak digital yang lebih hidup dan berkarakter.

IP Information

ip_address	188.114.96.7
country	-
network_name	Cloudflare Inc
asn	AS13335

ip_address	188.114.97.7
country	-
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 Cloud	IaaS
Google Cloud Trace	Performance
Firebase	Databases, Development
Google Analytics	Analytics
HTTP/3	Miscellaneous
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Cloudflare	CDN
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://capt77quantum.com/	auth.strategy	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: auth.strategy=custom

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	Method	Parameters	Evidence
https://capt77quantum.com/	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: <form class="header-right-form" data-v-876cf4d4=""><div data-v-876cf4d4=""><div class="form-flex" data-v-876cf4d4=""><div class="form-group" data-v-876cf4d4=""><input class="form-control untouched pristine" data-v-876cf4d4="" name="username" placeholder="" type="text" value=""/> <span class="error absolute username" data-v-876cf4d4=""></span></div> <div class="form-group dflex vertical-align-center" data-v-876cf4d4="" style="position:relative;"><input autocomplete="" class="form-control mx-1 untouched pristine" data-v-876cf4d4="" name="current-password" placeholder="" type="password" value=""/> <svg aria-hidden="true" class="pointer form-eye svg-inline--fa fa-eye-slash" data-icon="eye-slash" data-prefix="fas" data-v-876cf4d4="" focusable="false" role="img" style="bottom:unset;width:1.25em;" viewbox="0 0 640 512" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" d="M320 400c-75.85 0-137.25-58.71-142.9-133.11L72.2 185.82c-13.79 17.3-26.48 35.59-36.72 55.59a32.35 32.35 0 0 0 0 29.19C89.71 376.41 197.07 448 320 448c26.91 0 52.87-4 77.89-10.46L346 397.39a144.13 144.13 0 0 1-26 2.61zm313.82 58.1l-110.55-85.44a331.25 331.25 0 0 0 81.25-102.07 32.35 32.35 0 0 0 0-29.19C550.29 135.59 442.93 64 320 64a308.15 308.15 0 0 0-147.32 37.7L45.46 3.37A16 16 0 0 0 23 6.18L3.37 31.45A16 16 0 0 0 6.18 53.9l588.36 454.73a16 16 0 0 0 22.46-2.81l19.64-25.27a16 16 0 0 0-2.82-22.45zm-183.72-142l-39.3-30.38A94.75 94.75 0 0 0 416 256a94.76 94.76 0 0 0-121.31-92.21A47.65 47.65 0 0 1 304 192a46.64 46.64 0 0 1-1.54 10l-73.61-56.89A142.31 142.31 0 0 1 320 112a143.92 143.92 0 0 1 144 1... (truncated)</svg></div></div></div></form>

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.

Evidence

URL
https://capt77quantum.com/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	Evidence
https://capt77quantum.com/	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
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Google Cloud	IaaS
Google Cloud Trace	Performance
Firebase	Databases, Development
Google Analytics	Analytics
HTTP/3	Miscellaneous
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Cloudflare	CDN
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	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

URL	Method	Parameters	Evidence
https://capt77quantum.com/	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: captmaster10@gmail.com

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

Evidence

URL
Missing: https://capt77quantum.com/.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.

Evidence

URL Evidence

URL	Evidence
https://capt77quantum.com/	`<input type="text" placeholder="" name="username" value="" class="form-control untouched pristine" data-v-876cf4d4> <input placeholder="" name="current-password" autocomplete="" type="password" value="" class="form-control mx-1 untouched pristine" data-v-876cf4d4> <button id="login-button-desktop" class="cta cta-greylight cta-xs text-uppercase text-white cta-transparant-light" data-v-876cf4d4><!----> </button>`

https://capt77quantum.com/

<input type="text" placeholder="" name="username" value="" class="form-control untouched pristine" data-v-876cf4d4> <input placeholder="" name="current-password" autocomplete="" type="password" value="" class="form-control mx-1 untouched pristine" data-v-876cf4d4> <button id="login-button-desktop" class="cta cta-greylight cta-xs text-uppercase text-white cta-transparant-light" data-v-876cf4d4> </button>

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.

Infrastructure Vulnerabilities

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.

Operating System	Accuracy
FreeBSD 11.0-STABLE	91%

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.

Evidence

Software / Version	Category
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Firebase	Databases, Development
Google Cloud	IaaS
Vue.js	JavaScript frameworks
reCAPTCHA	Security
HSTS	Security
Google Cloud Trace	Performance
Cloudflare	CDN
HTTP/3	Miscellaneous
Google Analytics	Analytics
Google Tag Manager	Tag managers

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.

Evidence

Domain Queried	DNS Record Type	Description	Value
capt77quantum.com	A	IPv4 address	188.114.97.7
capt77quantum.com	A	IPv4 address	188.114.96.7
capt77quantum.com	NS	Name server	daniella.ns.cloudflare.com
capt77quantum.com	NS	Name server	yadiel.ns.cloudflare.com
capt77quantum.com	SOA	Start of Authority	daniella.ns.cloudflare.com. dns.cloudflare.com. 2388708186 10000 2400 604800 1800
capt77quantum.com	AAAA	IPv6 address	2a06:98c1:3121::7
capt77quantum.com	AAAA	IPv6 address	2a06:98c1:3120::7

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.