Vulnerability Scan Result

Target:

http://henderson10english.wordpress.com/ (redirect)

Scanned target: https://henderson10english.wordpress.com/

Submitted: Jun 20, 2026 from NI

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

http://henderson10english.wordpress.com/

Title:	Year 10 English \| 2016
Description:	2016

IP Information

ip_address	192.0.78.12
country	US
network_name	Automattic, Inc.
asn	AS2635

ip_address	192.0.78.13
country	US
network_name	Automattic, Inc.
asn	AS2635

Open Ports

80/tcp	http	nginx -
443/tcp	https	nginx -

Web Technologies

Software / Version	Category
Amazon Advertising	Advertising
Google Publisher Tag	Advertising
Google Font API	Font scripts
Google Analytics	Analytics
ID5	Advertising
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
Preact	JavaScript libraries
DoubleClick Floodlight	Advertising
Swiper	JavaScript libraries
Priority Hints	Performance
WordAds	Advertising
WordPress.com	PaaS
WordPress	CMS, Blogs
HSTS	Security
RSS	Miscellaneous

Web Application Vulnerabilities

Evidence

URL	Evidence
https://henderson10english.wordpress.com/	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
https://henderson10english.wordpress.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	Method	Parameters	Evidence
https://henderson10english.wordpress.com/	GET	Headers: User-Agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	Error message internal server error found in: `oo many requests.': 'too many requests.', 'internal server error.': 'internal server error.', 'is this you?`

Vulnerability description

We noticed that the target application does not properly handle exceptional conditions, leading to error messages that reveal sensitive information.

Risk description

The risk is that an attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application.

Recommendation

It is recommended treating all exceptions of the application flow. Ensure that error messages only contain minimal details.

Classification

CWE	CWE-209
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Amazon Advertising	Advertising
Google Publisher Tag	Advertising
Google Font API	Font scripts
Google Analytics	Analytics
ID5	Advertising
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
Preact	JavaScript libraries
DoubleClick Floodlight	Advertising
Swiper	JavaScript libraries
Priority Hints	Performance
WordAds	Advertising
WordPress.com	PaaS
WordPress	CMS, Blogs
HSTS	Security
RSS	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.

Classification

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

Evidence

URL	Evidence
https://henderson10english.wordpress.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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://henderson10english.wordpress.com/	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
Missing: https://henderson10english.wordpress.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.

Classification

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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Nginx	Web servers, Reverse proxies
WordPress.com	PaaS
ID5	Advertising
Google Publisher Tag	Advertising
DoubleClick Floodlight	Advertising
WordAds	Advertising
Swiper	JavaScript libraries
Priority Hints	Performance
Twitter Emoji (Twemoji)	Font scripts
Google Analytics	Analytics
Preact	JavaScript libraries
Amazon Advertising	Advertising
HSTS	Security
Open Graph	Miscellaneous
Gravatar	Miscellaneous
RSS	Miscellaneous
Google Font API	Font scripts

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
henderson10english.wordpress.com	A	IPv4 address	192.0.78.12
henderson10english.wordpress.com	A	IPv4 address	192.0.78.13
henderson10english.wordpress.com	CNAME	Canonical name	lb.wordpress.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.