Vulnerability Scan Result

Target:

http://go-proxy-bing.z2286332177-53a.workers.dev/

Scanned target: http://go-proxy-bing.z2286332177-53a.workers.dev/

Submitted: Jun 09, 2026 from FM

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	BingAI - 聊天
Description:	No description found

IP Information

ip_address	188.114.97.3
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	188.114.96.3
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 Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
GitHub Pages	PaaS
PHP	Programming languages
DoubleClick Floodlight	Advertising
Tailwind CSS	UI frameworks
Baidu Analytics (百度统计)	Analytics
WordPress	CMS, Blogs
Cloudflare	CDN
Fastly	CDN
Google Tag Manager	Tag managers
HSTS	Security
Varnish	Caching

Web Application Vulnerabilities

Evidence

URL	Response URL	Evidence
http://go-proxy-bing.z2286332177-53a.workers.dev/	http://go-proxy-bing.z2286332177-53a.workers.dev/	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://go-proxy-bing.z2286332177-53a.workers.dev/	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'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.`

http://go-proxy-bing.z2286332177-53a.workers.dev/

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'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.

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

Evidence

Software / Version	Category
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
GitHub Pages	PaaS
PHP	Programming languages
DoubleClick Floodlight	Advertising
Tailwind CSS	UI frameworks
Baidu Analytics (百度统计)	Analytics
WordPress	CMS, Blogs
Cloudflare	CDN
Fastly	CDN
Google Tag Manager	Tag managers
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.

Classification

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

Evidence

URL
Missing: http://go-proxy-bing.z2286332177-53a.workers.dev/.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

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
go-proxy-bing.z2286332177-53a.workers.dev	A	IPv4 address	188.114.97.3
go-proxy-bing.z2286332177-53a.workers.dev	A	IPv4 address	188.114.96.3
go-proxy-bing.z2286332177-53a.workers.dev	AAAA	IPv6 address	2a06:98c1:3120::3
go-proxy-bing.z2286332177-53a.workers.dev	AAAA	IPv6 address	2a06:98c1:3121::3

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
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Tailwind CSS	UI frameworks
Varnish	Caching
GitHub Pages	PaaS
Baidu Analytics (百度统计)	Analytics
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
Fastly	CDN
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
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Tailwind CSS	UI frameworks
Varnish	Caching
GitHub Pages	PaaS
Baidu Analytics (百度统计)	Analytics
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
Fastly	CDN
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
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Tailwind CSS	UI frameworks
Varnish	Caching
GitHub Pages	PaaS
Baidu Analytics (百度统计)	Analytics
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
Fastly	CDN
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
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Varnish	Caching
GitHub Pages	PaaS
Google Analytics	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
Fastly	CDN
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
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Varnish	Caching
GitHub Pages	PaaS
Google Analytics	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
Fastly	CDN
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.