Vulnerability Scan Result
| Title: | Doradztwo w Zakresie Ochrony Danych Osobowych - Wsparcie Dla Usług Prawnych | iSecure |
| Description: | Jako inspektorzy ochrony danych osobowych z iSecure oferujemy doradztwo w zakresie RODO oraz pełen zakres innych usług. Zapewniamy doradztwo w zakresie danych osobowych. |
| ip_address | 64.227.120.61 |
| country | DE  |
| network_name | DigitalOcean |
| asn | AS14061 |
21/tcp | ftp | ProFTPD - |
22/tcp | ssh | OpenSSH 8.9p1 Ubuntu 3ubuntu0.13 |
25/tcp | smtp | Postfix smtpd - |
53/tcp | domain | - - |
80/tcp | http | nginx - |
106/tcp | tcpwrapped | - - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | nginx - |
465/tcp | smtp | Postfix smtpd - |
993/tcp | imap | Dovecot imapd - |
995/tcp | pop3 | Dovecot pop3d - |
8443/tcp | https | sw-cp-server - |
| Software / Version | Category |
|---|---|
| Clipboard.js | JavaScript libraries |
| Contact Form 7 6.1.4 | WordPress plugins, Form builders |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Font API | Font scripts |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP 8.2.30 | Programming languages |
| ProfilePress 4.16.9 | WordPress plugins |
| MailerLite plugin | WordPress plugins |
| Select2 | JavaScript libraries |
| PWA | Miscellaneous |
| WooCommerce 10.4.3 | Ecommerce, WordPress plugins |
| WordPress | CMS, Blogs |
| Polylang | WordPress plugins, Translation |
| Cookiebot | Cookie compliance |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| MailerLite | Email, Marketing automation |
| HSTS | Security |
| W3 Total Cache | Caching, WordPress plugins |
| Yoast SEO 26.8 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Clipboard.js | JavaScript libraries |
| Contact Form 7 6.1.4 | WordPress plugins, Form builders |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Font API | Font scripts |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP 8.2.30 | Programming languages |
| ProfilePress 4.16.9 | WordPress plugins |
| MailerLite plugin | WordPress plugins |
| Select2 | JavaScript libraries |
| PWA | Miscellaneous |
| WooCommerce 10.4.3 | Ecommerce, WordPress plugins |
| WordPress | CMS, Blogs |
| Polylang | WordPress plugins, Translation |
| Cookiebot | Cookie compliance |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| MailerLite | Email, Marketing automation |
| HSTS | Security |
| W3 Total Cache | Caching, WordPress plugins |
| Yoast SEO 26.8 | SEO, WordPress plugins |
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
| URL | Evidence |
|---|---|
| https://www.isecure.pl/ | 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 |
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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.isecure.pl/ | 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 | Email Address: kontakt@isecure.pl |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp ProFTPD
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 2026-02-03 08:30 EET Nmap scan report for www.isecure.pl (64.227.120.61) Host is up (0.015s latency). rDNS record for 64.227.120.61: ironman.eagerdots.com
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 Dovecot pop3d |_pop3-capabilities: TOP UIDL SASL(PLAIN LOGIN DIGEST-MD5 CRAM-MD5) RESP-CODES PIPELINING APOP USER CAPA AUTH-RESP-CODE Service Info: Host: ironman
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 6.67 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
| Software / Version | Category |
|---|---|
| Plesk | Hosting panels |
| Nginx | Web servers, Reverse proxies |
| RequireJS | JavaScript frameworks |
| Prototype | JavaScript frameworks |
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
| Operating System | Accuracy |
|---|---|
| Linux 5.0 - 5.4 | 98% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP 8.2.30 | Programming languages |
| Contact Form 7 6.1.4 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| WooCommerce 10.4.3 | Ecommerce, WordPress plugins |
| W3 Total Cache | Caching, WordPress plugins |
| MailerLite plugin | WordPress plugins |
| ProfilePress 4.16.9 | WordPress plugins |
| Yoast SEO 26.8 | SEO, WordPress plugins |
| MailerLite | Email, Marketing automation |
| Select2 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Cookiebot | Cookie compliance |
| HSTS | Security |
| Polylang | WordPress plugins, Translation |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
| Google Font API | Font scripts |
| PWA | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.isecure.pl | A | IPv4 address | 64.227.120.61 |
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 |
| MySQL | Databases |
| PHP 8.2.30 | Programming languages |
| Contact Form 7 6.1.4 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| WooCommerce 10.4.3 | Ecommerce, WordPress plugins |
| W3 Total Cache | Caching, WordPress plugins |
| MailerLite plugin | WordPress plugins |
| ProfilePress 4.16.9 | WordPress plugins |
| Yoast SEO 26.8 | SEO, WordPress plugins |
| MailerLite | Email, Marketing automation |
| Select2 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Cookiebot | Cookie compliance |
| HSTS | Security |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
| Polylang | WordPress plugins, Translation |
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.