Vulnerability Scan Result

Target:

https://admin.argenteuilenpoche.fr/ (redirect)

Scanned target: https://admin.argenteuilenpoche.fr/connexion?redirect=/

Submitted: Oct 15, 2025 from VA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	360° Citiz - Administration
Description:	Votre territoire en un clic

IP Information

ip_address	13.37.79.6
country	FR
network_name	Amazon Inc
asn	AS16509

ip_address	52.47.104.46
country	FR
network_name	Amazon Inc
asn	AS16509

Open Ports

80/tcp	http	envoy -
443/tcp	https	envoy -

Web Technologies

Software / Version	Category
Google Font API	Font scripts
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Open Graph	Miscellaneous
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Envoy	Reverse proxies

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://admin.argenteuilenpoche.fr/connexion	i18n_redirected	Set-Cookie: i18n_redirected=fr

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://admin.argenteuilenpoche.fr/connexion	i18n_redirected	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: i18n_redirected=fr

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
https://admin.argenteuilenpoche.fr/connexion	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
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://admin.argenteuilenpoche.fr/connexion	GET	Query: current-password=Secure123456$ email=example_email@example.com 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 Cookies: i18n_redirected=fr	Credit Card Number: 6005240933147666
https://admin.argenteuilenpoche.fr/connexion	GET	Query: redirect=/ 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 Cookies: i18n_redirected=fr	Credit Card Number: 4781150426161196

Vulnerability description

We noticed that this application does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. Sensitive data targeted usually consists of emails, credit card and social security numbers.

Risk description

The risk exists that sensitive personal information within the application could be accessed by unauthorized parties. This could lead to privacy violations, identity theft, or other forms of personal or corporate harm.

Recommendation

Compartmentalize the application to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

Evidence

URL	Evidence
https://admin.argenteuilenpoche.fr/connexion	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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://admin.argenteuilenpoche.fr/connexion	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

Software / Version	Category
Google Font API	Font scripts
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Open Graph	Miscellaneous
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Envoy	Reverse proxies

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	Method	Parameters	Evidence
https://admin.argenteuilenpoche.fr/connexion	GET	Query: current-password=Secure123456$ email=example_email@example.com 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 Cookies: i18n_redirected=fr	The following form sends inputs of type password plainly in the URL: ` Adresse email Mot de passe ... (truncated)
https://admin.argenteuilenpoche.fr/connexion	GET	Query: redirect=/ 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	The following form sends inputs of type password plainly in the URL: ` Adresse email Mot de passe ... (truncated)

Vulnerability description

We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.

Risk description

Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.

Recommendation

You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.

Evidence

URL	Evidence
https://admin.argenteuilenpoche.fr/connexion	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

Evidence

URL	Method	Parameters	Evidence
https://admin.argenteuilenpoche.fr/connexion	GET	Query: redirect=/ 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: clement.roullet@gmail.com no-reply@360smartcity.fr commande@antidots-group.com support@360smartcity.fr

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

Evidence

URL
Missing: https://admin.argenteuilenpoche.fr/.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.

Evidence

URL Evidence

URL	Evidence
https://admin.argenteuilenpoche.fr/connexion	<input name="email" type="email" class="bg-transparent w-full outline-none"> <input name="current-password" type="password" class="bg-transparent w-full outline-none"> <button type="submit" disabled="disabled" class="w-full py-2 px-10 bg-primary bg-gray-300 dark:bg-light-black-500 disabled:cursor-not-allowed disabled:opacity-40 rounded-lg transition-all outline-none focus:outline-none relative flex items-center justify-center text-white"><!----> <span><span class="font-semibold text-sm">Se connecter</span></span></button>

https://admin.argenteuilenpoche.fr/connexion

<input name="email" type="email" class="bg-transparent w-full outline-none"> <input name="current-password" type="password" class="bg-transparent w-full outline-none"> <button type="submit" disabled="disabled" class="w-full py-2 px-10 bg-primary bg-gray-300 dark:bg-light-black-500 disabled:cursor-not-allowed disabled:opacity-40 rounded-lg transition-all outline-none focus:outline-none relative flex items-center justify-center text-white"> <span><span class="font-semibold text-sm">Se connecter</span></span></button>

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Envoy	Reverse proxies
Vue.js	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

Domain Queried	DNS Record Type	Description	Value
admin.argenteuilenpoche.fr	A	IPv4 address	52.47.104.46
admin.argenteuilenpoche.fr	A	IPv4 address	13.37.79.6
admin.argenteuilenpoche.fr	TXT	Text record	"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/smartcitiz-argen/admin-ingress"

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.