Vulnerability Scan Result

Target:

http://audaceinviora.net/ (redirect)

Scanned target: https://audaceinviora.net/

Submitted: Jan 28, 2026 from MR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Audace Inviora - Piattaforma Ufficiale \| Trading IA 2025 \| Oltre 10.000 Recensioni
Description:	Audace Inviora - La piattaforma di investimento basata su IA per operazioni profittevoli con le criptovalute. Strategie di trading automatizzate con un profitto giornaliero fino a 950 €. Investimento sicuro per gli investitori italiani.

IP Information

ip_address	172.67.153.48
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.21.32.177
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
HTTP/3	Miscellaneous
Open Graph	Miscellaneous
Tailwind CSS	UI frameworks
Cloudflare	CDN
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://audaceinviora.net/validation/thankyou.php	PHPSESSID	Set-Cookie: PHPSESSID=u278jgha1s5alu38n8s3hmqah6

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://audaceinviora.net/validation/thankyou.php	PHPSESSID	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=u278jgha1s5alu38n8s3hmqah6

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://audaceinviora.net/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. 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: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: https: URI in script-src allows the execution of unsafe scripts. default-src: data: URI in default-src allows the execution of unsafe scripts. default-src: https: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

https://audaceinviora.net/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. 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: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: https: URI in script-src allows the execution of unsafe scripts. default-src: data: URI in default-src allows the execution of unsafe scripts. default-src: https: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

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
OWASP Top 10 - 2021

Evidence

Software / Version	Category
HTTP/3	Miscellaneous
Open Graph	Miscellaneous
Tailwind CSS	UI frameworks
Cloudflare	CDN
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

URL
https://audaceinviora.net/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).

Evidence

URL	Method	Parameters	Evidence
https://audaceinviora.net/validation/thankyou.php	POST	Body: cid=1123123 cnt=phone email=example_email@example.com fph=tel full_lname=1d3d2d231d2dd4 full_name=1d3d2d231d2dd4 isa=false lng=it ocn=[] phc=it src=Audace Inviora Headers: Content-Type=application/x-www-form-urlencoded User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) Apple...	Possible API endpoint found at `/validation/thankyou.php`

Vulnerability description

We found API endpoints while crawling the given web application.

Risk description

These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.

Recommendation

Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.

Evidence

URL
Missing: https://audaceinviora.net/.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.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Cloudflare	CDN

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
Cloudflare	CDN

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
audaceinviora.net	A	IPv4 address	172.67.153.48
audaceinviora.net	A	IPv4 address	104.21.32.177
audaceinviora.net	NS	Name server	aarav.ns.cloudflare.com
audaceinviora.net	NS	Name server	lily.ns.cloudflare.com
audaceinviora.net	SOA	Start of Authority	aarav.ns.cloudflare.com. dns.cloudflare.com. 2394844491 10000 2400 604800 1800
audaceinviora.net	AAAA	IPv6 address	2606:4700:3037::6815:20b1
audaceinviora.net	AAAA	IPv6 address	2606:4700:3032::ac43:9930
audaceinviora.net	TXT	Text record	"google-site-verification=9wUdlpJYEofu1UsOsd8sZpdMCpaf3fshXjEt9OfKlSw"

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
Tailwind CSS	UI frameworks
HSTS	Security
Cloudflare	CDN
HTTP/3	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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
Cloudflare	CDN

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.