Vulnerability Scan Result

Target:

http://interhost.com/ (redirect)

Scanned target: https://www.interhost.com/

Submitted: May 15, 2026 from MR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	InterHost – Alojamiento con valor añadido
Description:	No description found

IP Information

ip_address	213.134.41.43
country	ES
network_name	Servicios de Hosting en Internet S.A.
asn	AS15919

Open Ports

80/tcp	http	Apache httpd 2.4.67
443/tcp	https	Apache httpd 2.4.67

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
cdnjs	CDN
Contact Form 7 6.1.5	WordPress plugins, Form builders
Debian	Operating systems
Google Font API	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
GSAP	JavaScript frameworks
Apache HTTP Server 2.4.67	Web servers
Isotope	JavaScript libraries
Jabmo	Marketing automation
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
Masonry	JavaScript libraries
Matomo Analytics	Analytics
MySQL	Databases
Open Graph	Miscellaneous
PhotoSwipe	Photo galleries, JavaScript libraries
PHP	Programming languages
Piwik PRO Core	Analytics
Priority Hints	Performance
WordPress 6.9.4	CMS, Blogs
wpBakery	Page builders, WordPress plugins
Cloudflare	CDN
Download Monitor 5.1.12	WordPress plugins
RSS	Miscellaneous
Slider Revolution 6.6.19	Widgets, Photo galleries

Web Application Vulnerabilities

Evidence

URL	Evidence
https://www.interhost.com/wp-content/uploads/2015	Found output resembling directory listing.
https://www.interhost.com/wp-includes/js/jquery/	Found output resembling directory listing.

Vulnerability description

We noticed that the target application's web server is affected by a Directory Listing vulnerability in its URL structure. Directory listing is enabled due to misconfigured server settings, allowing attackers to view all files and subdirectories on the server.

Risk description

The risk is that it's often the case that sensitive files are "hidden" among public files in that location and attackers can use this vulnerability to access them.

Recommendation

We recommend reconfiguring the web server in order to deny directory listing. Furthermore, you should verify that there are no sensitive files at the mentioned URLs.

Classification

CWE	CWE-548
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.interhost.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
https://www.interhost.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://www.interhost.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://www.interhost.com/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Amazon Web Services	PaaS
cdnjs	CDN
Contact Form 7 6.1.5	WordPress plugins, Form builders
Debian	Operating systems
Google Font API	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
GSAP	JavaScript frameworks
Apache HTTP Server 2.4.67	Web servers
Isotope	JavaScript libraries
Jabmo	Marketing automation
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
Masonry	JavaScript libraries
Matomo Analytics	Analytics
MySQL	Databases
Open Graph	Miscellaneous
PhotoSwipe	Photo galleries, JavaScript libraries
PHP	Programming languages
Piwik PRO Core	Analytics
Priority Hints	Performance
WordPress 6.9.4	CMS, Blogs
wpBakery	Page builders, WordPress plugins
Cloudflare	CDN
Download Monitor 5.1.12	WordPress plugins
RSS	Miscellaneous
Slider Revolution 6.6.19	Widgets, Photo galleries

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://www.interhost.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	Method	Parameters	Evidence
https://www.interhost.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: comercial@interhost.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://www.interhost.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 6.9.4	CMS, Blogs
Slider Revolution 6.7.38	Widgets, Photo galleries
MySQL	Databases
PHP	Programming languages
Debian	Operating systems
Contact Form 7 6.1.5	WordPress plugins, Form builders
GSAP	JavaScript frameworks
Amazon Web Services	PaaS
Apache HTTP Server 2.4.67	Web servers
wpBakery	Page builders, WordPress plugins
Download Monitor 5.1.12	WordPress plugins
Cloudflare	CDN
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries
cdnjs	CDN
Piwik PRO Core	Analytics
Jabmo	Marketing automation
Matomo Analytics	Analytics

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
Linux 4.15 - 5.6	100%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.interhost.com	A	IPv4 address	213.134.41.43
www.interhost.com	AAAA	IPv6 address	2001:b90:a:13:250:56ff:fe9c:a73

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.