Vulnerability Scan Result
| Title: | Uscila Propiedades – Inmobiliaria Alquiler y Venta de inmuebles |
| Description: | No description found |
| ip_address | 200.85.188.22 |
| country | AR  |
| network_name | Alpha 2000 Soluciones Informaticas SRL |
| asn | AS28037 |
21/tcp | ftp | Pure-FTPd - |
25/tcp | smtp | - - |
80/tcp | http | Apache httpd - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | Apache httpd - |
465/tcp | smtp | Exim smtpd 4.99.2 |
587/tcp | smtp | Exim smtpd 4.99.2 |
993/tcp | imap | Dovecot imapd - |
995/tcp | pop3 | Dovecot pop3d - |
2080/tcp | https | cPanel httpd - |
2083/tcp | radsec | - - |
2087/tcp | eli | - - |
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| FancyBox 3.5.7 | JavaScript libraries |
| Font Awesome | Font scripts |
| Google Font API | Font scripts |
| FullCalendar 6.1.19 | Widgets |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.46.0 | JavaScript libraries |
| Apache HTTP Server | Web servers |
| Retina.js | JavaScript libraries |
| Isotope | JavaScript libraries |
| Joinchat | Live chat |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| ProgressBar.js 1.0.1 | JavaScript libraries |
| lit-element 4.1.1 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| Google Maps | Maps |
| Masonry | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| Priority Hints | Performance |
| WordPress 6.9.4 | CMS, Blogs |
| Cloudflare | CDN |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
| RSS | Miscellaneous |
| TypeScript | Programming languages |
| WhatsApp Business Chat | Live chat |
Web Application Vulnerabilities
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://www.uscilapropiedades.com.ar/ | http://www.uscilapropiedades.com.ar/ | 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-319 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| FancyBox 3.5.7 | JavaScript libraries |
| Font Awesome | Font scripts |
| Google Font API | Font scripts |
| FullCalendar 6.1.19 | Widgets |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.46.0 | JavaScript libraries |
| Apache HTTP Server | Web servers |
| Retina.js | JavaScript libraries |
| Isotope | JavaScript libraries |
| Joinchat | Live chat |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| ProgressBar.js 1.0.1 | JavaScript libraries |
| lit-element 4.1.1 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| Google Maps | Maps |
| Masonry | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| Priority Hints | Performance |
| WordPress 6.9.4 | CMS, Blogs |
| Cloudflare | CDN |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
| RSS | Miscellaneous |
| TypeScript | Programming languages |
| WhatsApp Business Chat | Live chat |
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 | Evidence |
|---|---|
| http://www.uscilapropiedades.com.ar/ | 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://www.uscilapropiedades.com.ar/ | 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 | Evidence |
|---|---|
| http://www.uscilapropiedades.com.ar/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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 |
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
We managed to detect a publicly accessible Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2026-05-15 20:33 EEST Nmap scan report for www.uscilapropiedades.com.ar (200.85.188.22) Host is up (0.24s latency). rDNS record for 200.85.188.22: mail3.alpha2000.com.ar
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 Dovecot pop3d |_pop3-capabilities: RESP-CODES TOP SASL(PLAIN LOGIN) CAPA PIPELINING AUTH-RESP-CODE UIDL USER
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 8.94 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
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp Pure-FTPd
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
| Software / Version | Category |
|---|---|
| WordPress 6.9.4 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Google Maps | Maps |
| Apache HTTP Server | Web servers |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| Lightbox | JavaScript libraries |
| WhatsApp Business Chat | Live chat |
| ProgressBar.js 1.0.1 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Joinchat | Live chat |
| Font Awesome | Font scripts |
| Underscore.js 1.13.7 | JavaScript libraries |
| 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
| Software / Version | Category |
|---|---|
| Basic | 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
| Software / Version | Category |
|---|---|
| WordPress 6.9.4 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Google Maps | Maps |
| Apache HTTP Server | Web servers |
| Elementor 4.0.8 | Page builders, WordPress plugins |
| Lightbox | JavaScript libraries |
| WhatsApp Business Chat | Live chat |
| ProgressBar.js 1.0.1 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Joinchat | Live chat |
| Font Awesome | Font scripts |
| HSTS | Security |
| Underscore.js 1.13.7 | JavaScript libraries |
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.uscilapropiedades.com.ar | A | IPv4 address | 200.85.188.22 |
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 3.10 - 3.12 | 92% |
Vulnerability description
OS Detection