Vulnerability Scan Result
| Title: | 欲望だらけ |
| Description: | No description found |
| ip_address | 162.43.107.124 |
| country | JP  |
| network_name | Xserver Inc |
| asn | AS131965 |
21/tcp | ftp | ProFTPD or KnFTPD - |
25/tcp | smtp | Postfix smtpd - |
80/tcp | http | nginx - |
110/tcp | pop3 | Courier pop3d - |
143/tcp | imap | Courier Imapd - |
443/tcp | https | nginx - |
465/tcp | smtp | Postfix smtpd - |
587/tcp | smtp | Postfix smtpd - |
993/tcp | imap | Courier Imapd - |
995/tcp | pop3 | Courier pop3d - |
| Software / Version | Category |
|---|---|
| Moshimo | Affiliate programs |
| cdnjs | CDN |
| Google Hosted Libraries | CDN |
| jQuery Migrate 3.0.1 | JavaScript libraries |
| Google Font API | Font scripts |
| jQuery 3.6.1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| jsDelivr | CDN |
| Quantcast Measure | Analytics |
| RSS | Miscellaneous |
Web Application Vulnerabilities
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://yokubou.punipunihou.site/ | http://yokubou.punipunihou.site/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| http://yokubou.punipunihou.site/ | 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 |
|---|---|
| http://yokubou.punipunihou.site/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Moshimo | Affiliate programs |
| cdnjs | CDN |
| Google Hosted Libraries | CDN |
| jQuery Migrate 3.0.1 | JavaScript libraries |
| Google Font API | Font scripts |
| jQuery 3.6.1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| jsDelivr | CDN |
| Quantcast Measure | Analytics |
| RSS | 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
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
Vulnerability description
Website is accessible.
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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp ProFTPD or KnFTPD
Vulnerability description
We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.
Risk description
Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.
Recommendation
We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.
Evidence
We managed to detect a publicly accessible Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2025-06-30 05:34 EEST Nmap scan report for yokubou.punipunihou.site (162.43.107.124) Host is up (0.25s latency). rDNS record for 162.43.107.124: sv6103.wpx.ne.jp
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 Courier pop3d |_pop3-capabilities: USER TOP PIPELINING IMPLEMENTATION(Courier Mail Server) LOGIN-DELAY(10) UIDL
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 11.45 seconds
Vulnerability description
We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.
Risk description
Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.
Recommendation
We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| yokubou.punipunihou.site | A | IPv4 address | 162.43.107.124 |
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
| Operating System | Accuracy |
|---|---|
| Linux 5.0 - 5.4 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Cloudflare | CDN |
| jQuery Migrate 3.0.1 | JavaScript libraries |
| jQuery 3.6.1 | JavaScript libraries |
| Google Hosted Libraries | CDN |
| cdnjs | CDN |
| Quantcast Measure | Analytics |
| Moshimo | Affiliate programs |
| jsDelivr | CDN |
| Google Font API | Font scripts |
| RSS | Miscellaneous |
| Open Graph | 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Cloudflare | CDN |
| jQuery Migrate 3.0.1 | JavaScript libraries |
| jQuery 3.6.1 | JavaScript libraries |
| Google Hosted Libraries | CDN |
| cdnjs | CDN |
| Quantcast Measure | Analytics |
| Moshimo | Affiliate programs |
| jsDelivr | CDN |
| Google Font API | Font scripts |
| RSS | Miscellaneous |
| Open Graph | 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.