Vulnerability Scan Result

Target:

https://wrcash189-safe.pro/

Scanned target: https://wrcash189-safe.pro/

Submitted: Jan 27, 2026 from PE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	WARUNGCASH189: Home
Description:	Home

IP Information

ip_address	172.67.154.97
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.21.48.167
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	http	cloudflare -

Web Technologies

Software / Version	Category
TikTok Pixel	Analytics
Facebook Pixel 2.9.252	Analytics
Bootstrap 4.5.3	UI frameworks
core-js 3.32.2	JavaScript libraries
Google Analytics	Analytics
HTTP/3	Miscellaneous
jQuery	JavaScript libraries
Moment.js 2.18.1	JavaScript libraries
Select2	JavaScript libraries
Snowplow Analytics	Analytics, IaaS
SweetAlert2	JavaScript libraries
Swiper	JavaScript libraries
Cloudflare	CDN
Google Tag Manager	Tag managers
LiveChat	Live chat
HSTS	Security

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2022-31129	7.5	0.0311	0.86446	moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.
CVE-2022-24785	7.5	0.013	0.79338	Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
CVE-2017-18214	7.5	0.00322	0.54776	The moment module before 2.19.3 for Node.js is prone to a regular expression denial of service via a crafted date string, a different vulnerability than CVE-2016-4055.

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

URL	Cookie Name	Evidence
https://wrcash189-safe.pro/	modal314, mpoplay_frontend_session	Set-Cookie: modal314=eyJpdiI6IlhwNHprcDUxbWU1U2l4UlRVQ2ZqTEE9PSIsInZhbHVlIjoicjY1aHhzY016MUlyMnVVU29GTkJIVE1tYUxLRnhEUWxBdlkrRjhKUTFoQlRQYW1SVmtrWlJHbHBMaHFmTGYxUyIsIm1hYyI6ImQ4OWQ0OWU0ZjNjYmU5NDlhZjlkM2NmZDA3NTE1ZjAyZGFmMzEzYjZmMjhlZGRkNjU3NTc5YjNhYTUyM2M5NjMiLCJ0YWciOiIifQ%3D%3D Set-Cookie: mpoplay_frontend_session=var38uqNKyJ20YsKMSJeEh1WIloFeBlUL9e4G0YQ

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://wrcash189-safe.pro/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	Method	Parameters	Evidence
https://wrcash189-safe.pro/	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	The following form sends inputs of type password plainly in the URL: <form name="login-form"> <div class="row"> <input autocomplete="off" name="usernameLogin" placeholder="Nama Pengguna" required="" style="text-transform: lowercase" type="text" value=""/> <div class="position-relative"> <input autocomplete="off" id="passwordLogin" name="passwordLogin" placeholder="Kata Sandi" required="" type="password" value=""/> <i class="toggle-password fas fa-eye-slash" style=" position: absolute; right:0.5rem; top:50%; transform:translateY(-50%); cursor:pointer; color:#808080; " toggle="#passwordLogin"></i> </div> <button class="btn-masuk" name="buttonLogin" type="submit">Masuk</button> <a class="btn-daftar" href="https://wrcash189-safe.pro/register" id="register">Daftar</a> </div> </form>
https://wrcash189-safe.pro/	GET	Query: passwordLogin=Secure123456$ usernameLogin=1d3d2d231d2dd4 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 Cookies: XSRF-TOKEN=eyJpdiI6Im0wQzBNVE1VdDQ2RnRnQWdncVBjY0E9PSIsInZhbHVlIjoiRmlO...	The following form sends inputs of type password plainly in the URL: <form name="login-form"> <div class="form-item"> <div class="item-title">Nama Pengguna</div> <input autocomplete="off" maxlength="25" minlength="1" name="usernameLogin" placeholder="Nama Pengguna" required="" style="text-transform: lowercase" type="text" value=""/> </div> <div class="form-item"> <div class="item-title">Kata Sandi</div> <div class="position-relative"> <input autocomplete="off" id="passwordLogin2" maxlength="50" minlength="5" name="passwordLogin" placeholder="Kata Sandi" required="" type="password" value=""/> <i class="toggle-password fas fa-eye-slash" style=" position: absolute; right:0.5rem; top:50%; transform:translateY(-50%); cursor:pointer; color:#808080; " toggle="#passwordLogin2"></i> </div> </div> <div class="form-forgot"> <a href="https://wrcash189-safe.pro/forgot-password">Lupa Kata Sandi ?</a> </div> <div class="form-button"> <button class="button-login" name="buttonLogin" type="submit">Masuk</button> </div> </form>

Vulnerability description

We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.

Risk description

Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.

Recommendation

You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.

Evidence

URL Evidence

URL	Evidence
https://wrcash189-safe.pro/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. object-src: We recommend restricting object-src to 'none'. default-src: http: URI in default-src allows the execution of unsafe scripts. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: https: URI in default-src allows the execution of unsafe scripts. 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'.

https://wrcash189-safe.pro/

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

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

Software / Version	Category
TikTok Pixel	Analytics
Facebook Pixel 2.9.252	Analytics
Bootstrap 4.5.3	UI frameworks
core-js 3.32.2	JavaScript libraries
Google Analytics	Analytics
HTTP/3	Miscellaneous
jQuery	JavaScript libraries
Moment.js 2.18.1	JavaScript libraries
Select2	JavaScript libraries
Snowplow Analytics	Analytics, IaaS
SweetAlert2	JavaScript libraries
Swiper	JavaScript libraries
Cloudflare	CDN
Google Tag Manager	Tag managers
LiveChat	Live chat
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	Method	Summary
https://wrcash189-safe.pro/	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

Evidence

Domain Queried	DNS Record Type	Description	Value
wrcash189-safe.pro	SPF	Sender Policy Framework	"v=spf1 mx a ~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

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
HSTS	Security
Cloudflare	CDN
HTTP/3	Miscellaneous
jQuery	JavaScript libraries
Google Tag Manager	Tag managers
Google 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
FreeBSD 11.0-STABLE	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

Domain Queried	DNS Record Type	Description	Value
wrcash189-safe.pro	A	IPv4 address	172.67.154.97
wrcash189-safe.pro	A	IPv4 address	104.21.48.167
wrcash189-safe.pro	NS	Name server	david.ns.cloudflare.com
wrcash189-safe.pro	NS	Name server	keira.ns.cloudflare.com
wrcash189-safe.pro	SOA	Start of Authority	david.ns.cloudflare.com. dns.cloudflare.com. 2394983474 10000 2400 604800 1800
wrcash189-safe.pro	AAAA	IPv6 address	2606:4700:3031::ac43:9a61
wrcash189-safe.pro	AAAA	IPv6 address	2606:4700:3032::6815:30a7
wrcash189-safe.pro	SPF	Sender Policy Framework	"v=spf1 mx a ~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.