Vulnerability Scan Result

Target:

https://hellosafe.ph/

Scanned target: https://hellosafe.ph/

Submitted: Jun 11, 2026 from AR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	hellosafe.ph \| N°1 in financial product comparison
Description:	Hundreds of instant, free, and anonymous comparators to help you make the best financial decisions.

IP Information

ip_address	172.67.131.152
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.21.4.31
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	https-alt	cloudflare -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Microsoft Clarity	Analytics
Font Awesome	Font scripts
core-js 3.45.1	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Next.js 14.2.5	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Next.js App Router	JavaScript frameworks, Web servers
PHP	Programming languages
React	JavaScript frameworks
Supabase	Development
DoubleClick Floodlight	Advertising
PWA	Miscellaneous
Webpack	Miscellaneous
Priority Hints	Performance
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
PostgreSQL	Databases

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2025-29927	9.1	0.93247	0.99822	Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.
CVE-2026-44578	8.6	0.02829	0.84774	Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. This vulnerability is fixed in 15.5.16 and 16.2.5.
CVE-2026-44573	7.5	0.00351	0.26813	Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5.
CVE-2025-67779	7.5	0.1888	0.96925	It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.
CVE-2025-55184	7.5	0.65592	0.99165	A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Microsoft Clarity	Analytics
Font Awesome	Font scripts
core-js 3.45.1	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Next.js 14.2.5	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Next.js App Router	JavaScript frameworks, Web servers
PHP	Programming languages
React	JavaScript frameworks
Supabase	Development
DoubleClick Floodlight	Advertising
PWA	Miscellaneous
Webpack	Miscellaneous
Priority Hints	Performance
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
PostgreSQL	Databases

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
https://hellosafe.ph/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://hellosafe.ph/	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

URL	Evidence
https://hellosafe.ph/	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	Evidence
https://hellosafe.ph/	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	Evidence
https://hellosafe.ph/	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	Method	Parameters	Evidence
https://hellosafe.ph/	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	Operating system paths found in the HTTP response: `/chunks/app/universal/%5B`

Vulnerability description

We found operating system paths returned in a HTTP response.

Risk description

The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.

Recommendation

Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.

Classification

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

Evidence

URL
Missing: https://hellosafe.ph/.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

Domain Queried	DNS Record Type	Description	Value
hellosafe.ph	SPF	Sender Policy Framework	"v=spf1 include:spf.mailjet.com include:_mailcust.gandi.net include:_spf.google.com ~all"

Vulnerability description

We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.

Risk description

The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.

Recommendation

We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.

Evidence

Domain Queried	DNS Record Type	Description	Value
hellosafe.ph	TXT	Text record	"google-site-verification=E7DKEJnWx5vskncB-RpXz_OQjXMpSKrHogs0gCkVOwI"
hellosafe.ph	TXT	Text record	"google-site-verification=Xc335U07e8NKLITQ0dfSnYs1h8KM6kI2RhBzOMe7qP8"

Vulnerability description

We found that the target server has no DMARC policy configured. A missing DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy means that the domain is not enforcing any DMARC policies to protect against email spoofing and phishing attacks. Without DMARC, even if SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) are configured, there is no mechanism to tell receiving email servers how to handle messages that fail authentication. This leaves the domain vulnerable to abuse, such as email spoofing and impersonation.

Risk description

Without a DMARC policy, your domain is highly vulnerable to email spoofing, allowing attackers to impersonate your brand and send fraudulent emails that appear legitimate. This can lead to phishing attacks targeting your customers, employees, or partners, potentially resulting in stolen credentials, financial loss, or unauthorized access to sensitive systems. Additionally, repeated spoofing attempts can severely damage your brand's reputation, as recipients may lose trust in communications from your domain, associating your brand with malicious activity. The absence of DMARC also prevents you from monitoring and mitigating email-based attacks, leaving your domain exposed to ongoing abuse.

Recommendation

We recommend implementing a DMARC policy for your domain. Start by configuring a DMARC record with a policy of p=none, which will allow you to monitor email flows without impacting legitimate emails. This initial setup helps identify how emails from your domain are being processed by recipient servers. Once you’ve verified that legitimate emails are passing SPF and DKIM checks, you can gradually enforce stricter policies like p=quarantine or p=reject to protect against spoofing and phishing attacks. Additionally, include rua and ruf email addresses in the DMARC record to receive aggregate and forensic reports. These reports will provide valuable insights into authentication failures and help you detect any spoofing attempts.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
Cloudflare	CDN

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

Software / Version	Category
Cloudflare	CDN

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

Software / Version	Category
Cloudflare	CDN

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
hellosafe.ph	A	IPv4 address	104.21.4.31
hellosafe.ph	A	IPv4 address	172.67.131.152
hellosafe.ph	NS	Name server	eloise.ns.cloudflare.com
hellosafe.ph	NS	Name server	keenan.ns.cloudflare.com
hellosafe.ph	MX	Mail server	1 aspmx.l.google.com
hellosafe.ph	MX	Mail server	10 alt3.aspmx.l.google.com
hellosafe.ph	MX	Mail server	10 alt4.aspmx.l.google.com
hellosafe.ph	MX	Mail server	5 alt1.aspmx.l.google.com
hellosafe.ph	MX	Mail server	5 alt2.aspmx.l.google.com
hellosafe.ph	SOA	Start of Authority	eloise.ns.cloudflare.com. dns.cloudflare.com. 2406679573 10000 2400 604800 1800
hellosafe.ph	AAAA	IPv6 address	2606:4700:3034::6815:41f
hellosafe.ph	AAAA	IPv6 address	2606:4700:3034::ac43:8398
hellosafe.ph	TXT	Text record	"google-site-verification=E7DKEJnWx5vskncB-RpXz_OQjXMpSKrHogs0gCkVOwI"
hellosafe.ph	TXT	Text record	"google-site-verification=Xc335U07e8NKLITQ0dfSnYs1h8KM6kI2RhBzOMe7qP8"
hellosafe.ph	SPF	Sender Policy Framework	"v=spf1 include:spf.mailjet.com include:_mailcust.gandi.net include:_spf.google.com ~all"

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
WordPress	CMS, Blogs
Next.js	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Supabase	Development
MySQL	Databases
PHP	Programming languages
PostgreSQL	Databases
React	JavaScript frameworks
Amazon Web Services	PaaS
Next.js App Router	JavaScript frameworks, Web servers
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
DoubleClick Floodlight	Advertising
Cloudflare	CDN
Webpack	Miscellaneous
PWA	Miscellaneous
HTTP/3	Miscellaneous
Font Awesome	Font scripts
Priority Hints	Performance

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

DKIM selector	Key type	Key size	Value
google	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkvaDkw7Qllo3sIuTm5zlQ6vs8zoseAgYw9N33DDjntivRdKpXf0vwmzJVZc4shYYQhelyT7UXYP/O+Pl5Xl8nzfiS91Yas3cTXDG8W2369gsdH8/GDH09AD6Df/apBfnkDQ7hoKijFi4eRoy7ltTYlaa4zLVmufEzcH8/yDG46IrKvM1Td6XSc/IJ1U9+CrtJ" "YqIRIzqFgS//QVzGNpwsJ/Yo1lhFyBnPXif9p/yDwyt3CIL9xaAAPQ0GKZ9HUDEIDxIx+1tHY4NiwJxa/ZWO9/Rdr++U8R7MJnliB4QDE9GFwSyT0vQmTbeUTUtXqpMPiKW1HITQ70miAcn458uiQIDAQAB"
mailjet	rsa	1476	"k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuF2CRDLSjw6ZGgrClQVrfEIyjoT08OxrIAf/SfDUDC6+74qPkXaXmm0Q/XYd1akO5Oa9q8WlxKHpZkLrYHSr4yb8x9VHGTXQWEraZKad1N5z7DIiN1NQAJGKDu8LgR2f1CN0KUeHLZZTUhXQTHOGCs6MidxIw+hx4Ghed1UYyVEZKOC5WyO2pxbufqd8vEyNML+fSD10ba" "ay+fcodPmom3OnGYaHOnmBRSRE0xTTc+fNGx5smVJyEe27jnvEwseb0hdeMLu39ni7qK3iB1ESJB+y9nz7CeH1Ho115eQjMjJkzyKANlvcJq1elWAd2jIuZUpb23jDwcmz3sa41Cp5JQIDAQAB"