Vulnerability Scan Result

Target:

http://jump-byte.online/

Scanned target: http://jump-byte.online/

Submitted: Jun 18, 2026 from PS

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Azure Wave Inn - Premier Casino Hotel Destination
Description:	Experience luxury and excitement at Azure Wave Inn, your premier casino hotel destination. Indulge in world-class gaming, exquisite dining, and unparalleled accommodations. Discover why Azure Wave Inn is the ultimate choice for entertainment and relaxation.

IP Information

ip_address	104.21.21.226
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	172.67.200.238
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
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-alt	cloudflare -

Web Technologies

Software / Version	Category
HTTP/3	Miscellaneous
PHP	Programming languages
Cloudflare	CDN

Web Application Vulnerabilities

Evidence

URL	Response URL	Evidence
http://jump-byte.online/	http://jump-byte.online/	Communication is made over unsecure, unencrypted HTTP.

Vulnerability description

We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.

Risk description

The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).

Recommendation

We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.

Classification

CWE	CWE-319
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
http://jump-byte.online/sign-in.html	Password input detected over insecure HTTP. Login form: <form class="left-aligned-text"> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="you@example.com" required="" type="email"/> <label class="floating-label-style">Enter Email</label> </div> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="********" required="" type="password"/> <label class="floating-label-style">Enter Password</label> </div> <button class="primary-button-alert btn btn-primary" type="submit">Sign In</button> </form>

http://jump-byte.online/sign-in.html

Password input detected over insecure HTTP. Login form: <form class="left-aligned-text"> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="you@example.com" required="" type="email"/> <label class="floating-label-style">Enter Email</label> </div> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="********" required="" type="password"/> <label class="floating-label-style">Enter Password</label> </div> <button class="primary-button-alert btn btn-primary" type="submit">Sign In</button> </form>

Vulnerability description

We found that passwords are transmitted over a network without encryption. When users submit their passwords through an application or system, the lack of encryption means that the sensitive information is transmitted in plaintext, making it susceptible to interception and unauthorized access.

Risk description

The risk is that malicious actors could employ various techniques, such as packet sniffing or man-in-the-middle attacks, to capture plaintext passwords. Once intercepted, the attacker gains unauthorized access to user accounts, potentially leading to identity theft, unauthorized data access, or other malicious activities. The risk remains unchanged even if the password's form submission triggers a redirect response to an HTTPS page.

Recommendation

We recommend you to reconfigure the web server so it uses HTTPS - which encrypts the communication between the web browser and the server. This way, the attacker will not be able to obtain the clear-text passwords, even though he manages to intercept the network communication.

Classification

CWE	CWE-523
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
http://jump-byte.online/	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

URL	Evidence
http://jump-byte.online/	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
OWASP Top 10 - 2021

Evidence

Software / Version	Category
HTTP/3	Miscellaneous
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.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
http://jump-byte.online/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
http://jump-byte.online/	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	Method	Parameters	Evidence
http://jump-byte.online/sign-in.html	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="left-aligned-text"> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="you@example.com" required="" type="email"/> <label class="floating-label-style">Enter Email</label> </div> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="********" required="" type="password"/> <label class="floating-label-style">Enter Password</label> </div> <button class="primary-button-alert btn btn-primary" type="submit">Sign In</button> </form>
http://jump-byte.online/sign-up.html	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="left-aligned-text"> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="John Doe" required="" type="text"/> <label class="floating-label-style">Enter Full Name</label> </div> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="you@example.com" required="" type="email"/> <label class="floating-label-style">Enter Email</label> </div> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="********" required="" type="password"/> <label class="floating-label-style">Enter Password</label> </div> <div class="position-adjusted-margin form-floating"> <input class="styled-form-control form-control" placeholder="Confirm Password" required="" type="password"/> <label class="floating-label-style">Confirm Password</label> </div> <button class="primary-button-alert btn btn-primary" type="submit">Sign Up</button> </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.

Classification

CWE	CWE-598
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
http://jump-byte.online/sign-in.html	`<input required="" type="email" class="styled-form-control form-control" placeholder="you@example.com"> <input required="" type="password" class="styled-form-control form-control" placeholder="********"> <button type="submit" class="primary-button-alert btn btn-primary">Sign In</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.

Classification

CWE	CWE-287
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Operating System	Accuracy
FreeBSD 11.1-STABLE	91%

Evidence

Software / Version	Category
PHP	Programming languages
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
PHP	Programming languages
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
jump-byte.online	A	IPv4 address	104.21.21.226
jump-byte.online	A	IPv4 address	172.67.200.238
jump-byte.online	NS	Name server	angelina.ns.cloudflare.com
jump-byte.online	NS	Name server	newt.ns.cloudflare.com
jump-byte.online	SOA	Start of Authority	angelina.ns.cloudflare.com. dns.cloudflare.com. 2406851144 10000 2400 604800 1800
jump-byte.online	AAAA	IPv6 address	2606:4700:3030::ac43:c8ee
jump-byte.online	AAAA	IPv6 address	2606:4700:3030::6815:15e2

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.