Vulnerability Scan Result

Target:

https://cloud.mysecure.space/ (redirect)

Scanned target: https://cloud.mysecure.space/login

Submitted: May 02, 2026 from TT

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	Login – MySecure.Space
Description:	No description found

IP Information

ip_address	91.98.247.150
country	DE
network_name	Hetzner Online GmbH
asn	AS24940

Open Ports

80/tcp	http	OpenResty web app server -
443/tcp	https	OpenResty web app server -

Web Technologies

Software / Version	Category
Backbone.js 1.6.1	JavaScript frameworks
core-js 3.48.0	JavaScript libraries
Handlebars 4.7.8	JavaScript frameworks
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
Moment.js 2.30.1	JavaScript libraries
Nextcloud 32.0.6.1	Digital asset management, Miscellaneous
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
OpenResty	Web servers
ownCloud	Miscellaneous
PHP	Programming languages
Select2	JavaScript libraries
Underscore.js	JavaScript libraries
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Lodash 1.13.7	JavaScript libraries
HSTS	Security

Web Application Vulnerabilities

Evidence

URL
https://cloud.mysecure.space/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

URL	Evidence
https://cloud.mysecure.space/login	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. object-src: We recommend restricting object-src to 'none'.`

https://cloud.mysecure.space/login

Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is '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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Backbone.js 1.6.1	JavaScript frameworks
core-js 3.48.0	JavaScript libraries
Handlebars 4.7.8	JavaScript frameworks
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
Moment.js 2.30.1	JavaScript libraries
Nextcloud 32.0.6.1	Digital asset management, Miscellaneous
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
OpenResty	Web servers
ownCloud	Miscellaneous
PHP	Programming languages
Select2	JavaScript libraries
Underscore.js	JavaScript libraries
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Lodash 1.13.7	JavaScript libraries
HSTS	Security

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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
cloud.mysecure.space	A	IPv4 address	91.98.247.150
cloud.mysecure.space	MX	Mail server	10 mx.your-storageshare.de
cloud.mysecure.space	AAAA	IPv6 address	2a01:4f8:bacc:2:200::1116
cloud.mysecure.space	SPF	Sender Policy Framework	"v=spf1 a -all"
cloud.mysecure.space	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
cloud.mysecure.space	CNAME	Canonical name	nx365.your-storageshare.de

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
PHP	Programming languages
Nginx	Web servers, Reverse proxies
Vue.js	JavaScript frameworks
OpenResty	Web servers
HSTS	Security
Nextcloud	Digital asset management, 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.