Vulnerability Scan Result

Target:

http://sapondanaisriwan.github.io/ (redirect)

Scanned target: https://sapondanaisriwan.github.io/

Submitted: Nov 17, 2025 from GT

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Sapondanai Sriwan
Description:	Sapondanai Sriwan is just an average high school student who enjoys programming and creating interesting projects.

IP Information

ip_address	185.199.108.153
country	US
network_name	Fastly Inc
asn	AS54113

ip_address	185.199.109.153
country	US
network_name	Fastly Inc
asn	AS54113

ip_address	185.199.110.153
country	US
network_name	Fastly Inc
asn	AS54113

ip_address	185.199.111.153
country	US
network_name	Fastly Inc
asn	AS54113

Open Ports

80/tcp	http	GitHub.com -
443/tcp	https	GitHub.com -

Web Technologies

Software / Version	Category
Ko-fi	Widgets, Fundraising & donations
GitHub Pages	PaaS
Sectigo	SSL/TLS certificate authorities
Tailwind CSS	UI frameworks
Fastly	CDN
HSTS	Security
Varnish	Caching

Web Application Vulnerabilities

Evidence

URL	Evidence
https://sapondanaisriwan.github.io/	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	Evidence
https://sapondanaisriwan.github.io/	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
Ko-fi	Widgets, Fundraising & donations
GitHub Pages	PaaS
Sectigo	SSL/TLS certificate authorities
Tailwind CSS	UI frameworks
Fastly	CDN
HSTS	Security
Varnish	Caching

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	Evidence
https://sapondanaisriwan.github.io/images/svg	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`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'. object-src: We recommend restricting object-src to 'none'.`

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-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://sapondanaisriwan.github.io/	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

URL	Method	Parameters	Evidence
https://sapondanaisriwan.github.io/	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: sapondanaisriwan@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://sapondanaisriwan.github.io/.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.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Tailwind CSS	UI frameworks
Varnish	Caching
GitHub Pages	PaaS
Sectigo	SSL/TLS certificate authorities
HSTS	Security
Fastly	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
sapondanaisriwan.github.io	A	IPv4 address	185.199.108.153
sapondanaisriwan.github.io	A	IPv4 address	185.199.109.153
sapondanaisriwan.github.io	A	IPv4 address	185.199.110.153
sapondanaisriwan.github.io	A	IPv4 address	185.199.111.153
sapondanaisriwan.github.io	AAAA	IPv6 address	2606:50c0:8000::153
sapondanaisriwan.github.io	AAAA	IPv6 address	2606:50c0:8002::153
sapondanaisriwan.github.io	AAAA	IPv6 address	2606:50c0:8003::153
sapondanaisriwan.github.io	AAAA	IPv6 address	2606:50c0:8001::153
sapondanaisriwan.github.io	CAA	Certificate Authority Authorization	0 issue "digicert.com"
sapondanaisriwan.github.io	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
sapondanaisriwan.github.io	CAA	Certificate Authority Authorization	0 issue "sectigo.com"
sapondanaisriwan.github.io	CAA	Certificate Authority Authorization	0 issuewild "digicert.com"
sapondanaisriwan.github.io	CAA	Certificate Authority Authorization	0 issuewild "sectigo.com"

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.