Vulnerability Scan Result

Target:

http://arenza.store/ (redirect)

Scanned target: https://arenza.store/

Submitted: May 31, 2025 from CD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	Home - arenza.store
Description:	Welcome to Flawless StoreThe Best Skin Cleanser for YouShop Now New Arrivals Shop now Beauty Flawless SkinEnim lectus mauris faucibus turpis convallis ipsum odio lorem dignissim id odio sed enim nullam venenatis erat in cursus tortor tristique aliquam nulla quis.Aliquam scelerisque scelerisque ac laoreet laoreet faucibus vestibulum fringilla ut aliquet dictumst dignissim id eget cras

IP Information

IP address	92.113.16.254
Country	DE
AS number	-
Net name	-

Open Ports

No open ports were found.

Web Technologies

Software / Version	Category
All in One SEO Pack 4.8.2	SEO, WordPress plugins
Clipboard.js	JavaScript libraries
Gutenberg	WordPress plugins, Editors
jQuery Migrate 3.4.1	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
imagesLoaded 2.19.9	JavaScript libraries
jQuery	JavaScript libraries
Slick	JavaScript libraries
MySQL	Databases
PHP 8.2.27	Programming languages
Site Kit 1.153.0	Analytics, WordPress plugins
Underscore.js 1.13.7	JavaScript libraries
WooCommerce 9.8.5	Ecommerce, WordPress plugins
WordPress 6.8.1	CMS, Blogs
Astra 4.11.1	WordPress themes
Spectra 2.19.9	WordPress plugins
Hostinger	Hosting
RSS	Miscellaneous
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Evidence
https://arenza.store/	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://arenza.store/	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

URL	Evidence
https://arenza.store/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.`

https://arenza.store/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

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

Evidence

URL	Evidence
https://arenza.store/	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
All in One SEO Pack 4.8.2	SEO, WordPress plugins
Clipboard.js	JavaScript libraries
Gutenberg	WordPress plugins, Editors
jQuery Migrate 3.4.1	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
imagesLoaded 2.19.9	JavaScript libraries
jQuery	JavaScript libraries
Slick	JavaScript libraries
MySQL	Databases
PHP 8.2.27	Programming languages
Site Kit 1.153.0	Analytics, WordPress plugins
Underscore.js 1.13.7	JavaScript libraries
WooCommerce 9.8.5	Ecommerce, WordPress plugins
WordPress 6.8.1	CMS, Blogs
Astra 4.11.1	WordPress themes
Spectra 2.19.9	WordPress plugins
Hostinger	Hosting
RSS	Miscellaneous
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://arenza.store/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
Missing: https://arenza.store/.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

Evidence

URL	Method	Summary
https://arenza.store/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: OPTIONS,HEAD,GET,POST` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
arenza.store	A	IPv4 address	84.32.84.118
arenza.store	NS	Name server	ns1.dns-parking.com
arenza.store	NS	Name server	ns2.dns-parking.com
arenza.store	SOA	Start of Authority	ns1.dns-parking.com. dns.hostinger.com. 2025053014 10000 2400 604800 600
arenza.store	AAAA	IPv6 address	2a02:4780:84:cc79:3ee6:b25e:538b:11b4
arenza.store	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
arenza.store	CAA	Certificate Authority Authorization	0 issue "digicert.com"
arenza.store	CAA	Certificate Authority Authorization	0 issue "comodoca.com"
arenza.store	CAA	Certificate Authority Authorization	0 issuewild "comodoca.com"
arenza.store	CAA	Certificate Authority Authorization	0 issue "sectigo.com"
arenza.store	CAA	Certificate Authority Authorization	0 issue "pki.goog"
arenza.store	CAA	Certificate Authority Authorization	0 issuewild "pki.goog"
arenza.store	CAA	Certificate Authority Authorization	0 issuewild "sectigo.com"
arenza.store	CAA	Certificate Authority Authorization	0 issuewild "letsencrypt.org"
arenza.store	CAA	Certificate Authority Authorization	0 issue "globalsign.com"
arenza.store	CAA	Certificate Authority Authorization	0 issuewild "globalsign.com"
arenza.store	CAA	Certificate Authority Authorization	0 issuewild "digicert.com"

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.