Vulnerability Scan Result

Target:

https://status.manilatrack.com/

Scanned target: https://status.manilatrack.com/

Submitted: Dec 03, 2025 from TH

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Manila Status
Description:	No description found

IP Information

ip_address	142.132.149.97
country	DE
network_name	Hetzner Online GMBH
asn	AS24940

Open Ports

80/tcp	http	Caddy httpd -
443/tcp	https	- -

Web Technologies

Software / Version	Category
Caddy	Web servers
UIKit	UI frameworks
Go	Programming languages
Google Font API	Font scripts
jQuery 3.7.1	JavaScript libraries
Sentry	Issue trackers
UptimeRobot	Issue trackers
Webpack	Miscellaneous
Google Tag Manager	Tag managers
HSTS	Security

Web Application Vulnerabilities

Evidence

Software / Version	Category
Caddy	Web servers
UIKit	UI frameworks
Go	Programming languages
Google Font API	Font scripts
jQuery 3.7.1	JavaScript libraries
Sentry	Issue trackers
UptimeRobot	Issue trackers
Webpack	Miscellaneous
Google Tag Manager	Tag managers
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.

Evidence

URL
https://status.manilatrack.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

URL	Evidence
https://status.manilatrack.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing.`

https://status.manilatrack.com/

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

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

Evidence

URL	Method	Summary
https://status.manilatrack.com/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Operating System	Accuracy
Linux 4.15 - 5.6	100%

Evidence

Software / Version	Category
Sentry	Issue trackers
Go	Programming languages
UIKit	UI frameworks
Caddy	Web servers
Google Tag Manager	Tag managers
jQuery 3.7.1	JavaScript libraries
HSTS	Security
Webpack	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

Domain Queried	DNS Record Type	Description	Value
status.manilatrack.com	A	IPv4 address	142.132.149.97
status.manilatrack.com	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
status.manilatrack.com	CAA	Certificate Authority Authorization	0 issue "zerossl.com"
status.manilatrack.com	CNAME	Canonical name	stats.uptimerobot.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.