Vulnerability Scan Result

Target:

https://mariacestetica.sicom.me/

Scanned target: https://mariacestetica.sicom.me/

Submitted: May 24, 2025 from TV

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	María C Estética
Description:	No description found

IP Information

IP address	82.223.39.78
Country	ES
AS number	AS8560
Net name	Ionos Se

Open Ports

21/tcp	ftp	ProFTPD -
22/tcp	ssh	OpenSSH 8.9p1 Ubuntu 3ubuntu0.13
25/tcp	smtp	Postfix smtpd -
80/tcp	http	nginx -
110/tcp	pop3	Dovecot pop3d -
143/tcp	imap	Dovecot imapd -
443/tcp	https	nginx -
465/tcp	smtp	Postfix smtpd -
3306/tcp	mysql	MariaDB -
8443/tcp	https	sw-cp-server -

Web Technologies

Software / Version	Category
Clipboard.js	JavaScript libraries
Contact Form 7 6.0.6	WordPress plugins, Form builders
Elementor 3.29.0	Page builders, WordPress plugins
Font Awesome	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
Google Font API	Font scripts
imagesLoaded 5.0.0	JavaScript libraries
jQuery	JavaScript libraries
MailChimp	Marketing automation, Email
Moment.js	JavaScript libraries
MySQL	Databases
Nginx	Web servers, Reverse proxies
prettyPhoto	JavaScript libraries
OWL Carousel	JavaScript libraries
PHP 8.2.28	Programming languages
Swiper	JavaScript libraries
WooCommerce 9.8.5	Ecommerce, WordPress plugins
WordPress 6.8.1	CMS, Blogs
Lodash	JavaScript libraries
MailChimp for WordPress 4.10.3	WordPress plugins, Marketing automation
RSS	Miscellaneous
Slider Revolution 6.7.28	Widgets, Photo galleries
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Evidence
https://mariacestetica.sicom.me/	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	Evidence
https://mariacestetica.sicom.me/	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://mariacestetica.sicom.me/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

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

Evidence

URL	Evidence
https://mariacestetica.sicom.me/	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

Software / Version	Category
Clipboard.js	JavaScript libraries
Contact Form 7 6.0.6	WordPress plugins, Form builders
Elementor 3.29.0	Page builders, WordPress plugins
Font Awesome	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
Google Font API	Font scripts
imagesLoaded 5.0.0	JavaScript libraries
jQuery	JavaScript libraries
MailChimp	Marketing automation, Email
Moment.js	JavaScript libraries
MySQL	Databases
Nginx	Web servers, Reverse proxies
prettyPhoto	JavaScript libraries
OWL Carousel	JavaScript libraries
PHP 8.2.28	Programming languages
Swiper	JavaScript libraries
WooCommerce 9.8.5	Ecommerce, WordPress plugins
WordPress 6.8.1	CMS, Blogs
Lodash	JavaScript libraries
MailChimp for WordPress 4.10.3	WordPress plugins, Marketing automation
RSS	Miscellaneous
Slider Revolution 6.7.28	Widgets, Photo galleries
Cart Functionality	Ecommerce

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

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

Evidence

URL
https://mariacestetica.sicom.me/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).

Classification

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

Evidence

URL	Method	Parameters	Evidence
https://mariacestetica.sicom.me/	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: efrem@gruposicom.com needhelp@company.com

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	A6: Security Misconfiguration
OWASP Top 10 - 2021	A4: Insecure Design

Evidence

URL
Missing: https://mariacestetica.sicom.me/.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

We managed to detect a publicly accessible SSH service.

Starting Nmap ( https://nmap.org ) at 2025-05-24 03:55 EEST
Nmap scan report for mariacestetica.sicom.me (82.223.39.78)
Host is up (0.038s latency).
rDNS record for 82.223.39.78: server78.sicom.me

PORT   STATE SERVICE VERSION
22/tcp open  ssh     OpenSSH 8.9p1 Ubuntu 3ubuntu0.13 (Ubuntu Linux; protocol 2.0)
| ssh-auth-methods: 
|   Supported authentication methods: 
|     publickey
|_    password
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 1.35 seconds

Vulnerability description

We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.

Risk description

Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.

Recommendation

We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.

Evidence

We managed to detect a publicly accessible MySQL service.

PORT STATE SERVICE VERSION
3306/tcp open mysql MariaDB

Vulnerability description

We identified that the MySQL service is publicly accessible. MySQL serves as a common database for numerous web applications and services for data storage, making it a potential prime target for determined attackers.

Risk description

The risk exists that an attacker exploits this issue by launching a password-based attack on the MySQL service. Furthermore, they could exploit zero-day vulnerabilities to obtain remote access to the MySQL database server, thereby gaining complete control over its operating system and associated services. Such an attack could lead to the exposure of confidential or sensitive information.

Recommendation

We recommend turning off public Internet access to MySQL and opting for a Virtual Private Network (VPN) that enforces two-factor authentication (2FA). Avoid enabling direct user authentication to the MySQL service via the Internet, as this could enable attackers to engage in password-guessing and potentially initiate attacks leading to complete control. However, if the MySQL service is required to be directly accessible over the Internet, we recommend reconfiguring it to be accessible only from known IP addresses.

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

Domain Queried	DNS Record Type	Description	Value
mariacestetica.sicom.me	A	IPv4 address	82.223.39.78

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.

Operating System	Accuracy
Linux 5.0 - 5.4	100%

Evidence

Software / Version	Category
WordPress 6.8.1	CMS, Blogs
Slider Revolution 6.7.28	Widgets, Photo galleries
MySQL	Databases
PHP 8.2.28	Programming languages
Contact Form 7 6.0.6	WordPress plugins, Form builders
Nginx	Web servers, Reverse proxies
WooCommerce 9.8.5	Ecommerce, WordPress plugins
Elementor 3.29.0	Page builders, WordPress plugins
MailChimp	Marketing automation, Email
MailChimp for WordPress 4.10.3	WordPress plugins, Marketing automation
Slick	JavaScript libraries
Swiper	JavaScript libraries
prettyPhoto	JavaScript libraries
OWL Carousel	JavaScript libraries
Moment.js	JavaScript libraries
Lodash	JavaScript libraries
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries
imagesLoaded 5.0.0	JavaScript libraries
Font Awesome	Font scripts

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
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.