Vulnerability Scan Result

Target:

https://track.trackwise.me/

Scanned target: https://track.trackwise.me/

Submitted: May 04, 2026 from VN

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	Trackwise - Personal Finance & Savings Tracker
Description:	No description found

IP Information

ip_address	134.199.188.134
country	DE
network_name	DigitalOcean
asn	AS14061

Open Ports

22/tcp	ssh	OpenSSH 8.9p1 Ubuntu 3ubuntu0.15
80/tcp	http	Golang net/http server -
443/tcp	https	Golang net/http server -

Web Technologies

Software / Version	Category
Emotion	JavaScript frameworks, Development
Google Font API	Font scripts
MUI	UI frameworks
Nginx 1.29.4	Web servers, Reverse proxies
React	JavaScript frameworks
React Router 6	JavaScript frameworks
Unpkg	CDN
PWA	Miscellaneous
HSTS	Security

Web Application Vulnerabilities

Evidence

URL
https://track.trackwise.me/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://track.trackwise.me/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. object-src: We recommend restricting object-src to 'none'. 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: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: https: URI in script-src allows the execution of unsafe scripts.

https://track.trackwise.me/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. object-src: We recommend restricting object-src to 'none'. 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: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: https: URI in script-src allows the execution of unsafe scripts.

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
Emotion	JavaScript frameworks, Development
Google Font API	Font scripts
MUI	UI frameworks
Nginx 1.29.4	Web servers, Reverse proxies
React	JavaScript frameworks
React Router 6	JavaScript frameworks
Unpkg	CDN
PWA	Miscellaneous
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
track.trackwise.me	A	IPv4 address	134.199.188.134

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
Material UI	UI frameworks
Nginx 1.29.4	Web servers, Reverse proxies
React	JavaScript frameworks
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.