Vulnerability Scan Result

Target:

https://lovesoulpark.com/ (redirect)

Scanned target: https://lovesoulpark.com/index.php?m=Index&c=Index&a=index

Submitted: May 30, 2025 from TR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	lovesoulpark the world's most professional large-scale dating, love one of the platform, millions of beautiful handsome guy here waiting for you, you are still hesitant what?
Description:	lovesoulpark the world's most professional large-scale dating, love one of the platform, millions of beautiful handsome guy here waiting for you, you are still hesitant what?

IP Information

IP address	198.11.183.223
Country	US
AS number	AS45102
Net name	Alibaba Technology Co Ltd

Open Ports

No open ports were found.

Web Technologies

No technologies could be detected.

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://lovesoulpark.com/index.php	PHPSESSID	Set-Cookie: PHPSESSID=flqi2a1q02p2smho9v02v84nhh

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Cookie Name	Evidence
https://lovesoulpark.com/index.php	PHPSESSID	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=flqi2a1q02p2smho9v02v84nhh

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://lovesoulpark.com/index.php	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-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://lovesoulpark.com/index.php	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL Method Parameters Evidence

https://lovesoulpark.com/index.php

GET

Query: a=index c=Index l=ko-kr m=Index 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: PHPSESSID=r337t1qrs1enpvn1395nu3kgoa think_language=ko-kr

The following form sends inputs of type password plainly in the URL: `

어서 오세요 lovesoulpark

<!-- <td class="reg_td0">

비밀번호 확인 ... (truncated)

사서함

사용자 이름

암호

https://lovesoulpark.com/index.php

GET

Query: a=index c=Index m=Index 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: `

Welcome to lovesoulpark

<!-- <td class="reg_td0">

Confirm Password ... (truncated)

Username

Password

https://lovesoulpark.com/index.php

GET

Query: reg_alias=1d3d2d231d2dd4 reg_birth=1123123 reg_day=-1 reg_email=example_email@example.com reg_fid=1123123 reg_gender=male reg_md5pwd=1123123 reg_month=-1 reg_pp=1 reg_pwd=Secure123456$ reg_pwd2=Secure123456$ reg_sid=1123123 reg_year=-1 Headers: User-Agent=Mozilla/5.0 (Windows...

The following form sends inputs of type password plainly in the URL: `

Benvenuti alla lovesoulpark

<!-- <td class="reg_td0">

Conf... (truncated)

cassetta della posta
IL nome utente
password

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.

Classification

OWASP Top 10 - 2017
OWASP Top 10 - 2021	A4 - Insecure Design

Evidence

URL	Evidence
https://lovesoulpark.com/index.php	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://lovesoulpark.com/index.php	`<input class="reg_input" id="reg_email" name="reg_email" type="email"/> <input class="reg_input" id="reg_pwd" name="reg_pwd" type="password"/> <button id="head_login">Login</button>`

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Evidence

URL
Missing: https://lovesoulpark.com/.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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
lovesoulpark.com	A	IPv4 address	198.11.183.223
lovesoulpark.com	NS	Name server	dns28.hichina.com
lovesoulpark.com	NS	Name server	dns27.hichina.com
lovesoulpark.com	SOA	Start of Authority	dns27.hichina.com. hostmaster.hichina.com. 2025053012 3600 1200 86400 600

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.