Vulnerability Scan Result
| Title: | Au supermarché – Les Cahiers de l'Absurdie |
| Description: | No description found |
| ip_address | 195.5.171.242 |
| country | US  |
| network_name | DFINITY USA Research, LLC |
| asn | AS398485 |
| ip_address | 212.71.124.188 |
| country | CH  |
| network_name | EveryWare AG |
| asn | AS24951 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Twitter Ads | Advertising |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| Google Analytics GA4 | Analytics |
| imagesLoaded 4.1.4 | JavaScript libraries |
| jQuery 3.6.1 | JavaScript libraries |
| Masonry | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| Neve 3.4.5 | WordPress themes |
| Widgets | |
| WordPress 6.1.1 | CMS, Blogs |
| WordPress Block Editor | Page builders |
| ContentViews | Widgets, WordPress plugins |
| AddToAny | Widgets |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2024-31210 | 7.6 | 0.00994 | 0.77031 | WordPress is an open publishing platform for the Web. It's possible for a file of a type other than a zip file to be submitted as a new plugin by an administrative user on the Plugins -> Add New -> Upload Plugin screen in WordPress. If FTP credentials are requested for installation (in order to move the file into place outside of the `uploads` directory) then the uploaded file remains temporary available in the Media Library despite it not being allowed. If the `DISALLOW_FILE_EDIT` constant is set to `true` on the site _and_ FTP credentials are required when uploading a new theme or plugin, then this technically allows an RCE when the user would otherwise have no means of executing arbitrary PHP code. This issue _only_ affects Administrator level users on single site installations, and Super Admin level users on Multisite installations where it's otherwise expected that the user does not have permission to upload or execute arbitrary PHP code. Lower level users are not affected. Sites where the `DISALLOW_FILE_MODS` constant is set to `true` are not affected. Sites where an administrative user either does not need to enter FTP credentials or they have access to the valid FTP credentials, are not affected. The issue was fixed in WordPress 6.4.3 on January 30, 2024 and backported to versions 6.3.3, 6.2.4, 6.1.5, 6.0.7, 5.9.9, 5.8.9, 5.7.11, 5.6.13, 5.5.14, 5.4.15, 5.3.17, 5.2.20, 5.1.18, 5.0.21, 4.9.25, 2.8.24, 4.7.28, 4.6.28, 4.5.31, 4.4.32, 4.3.33, 4.2.37, and 4.1.40. A workaround is available. If the `DISALLOW_FILE_MODS` constant is defined as `true` then it will not be possible for any user to upload a plugin and therefore this issue will not be exploitable. |
| CVE-2024-4439 | 7.2 | 0.90817 | 0.99635 | WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in various versions up to 6.5.2 due to insufficient output escaping on the display name. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. In addition, it also makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that have the comment block present and display the comment author's avatar. |
| CVE-2023-38000 | 6.5 | 0.00347 | 0.57245 | Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions. |
| CVE-2022-3590 | 5.9 | 0.90761 | 0.9963 | WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden. |
| CVE-2023-2745 | 5.4 | 0.77175 | 0.98984 | WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://75gkk-2iaaa-aaaad-qemqq-cai.icp0.io/tag/au-supermarche/index.html | 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 |
|---|---|
| https://75gkk-2iaaa-aaaad-qemqq-cai.icp0.io/tag/au-supermarche/index.html | 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 |
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 | Evidence |
|---|---|
| https://75gkk-2iaaa-aaaad-qemqq-cai.icp0.io/tag/au-supermarche/index.html | 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 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://75gkk-2iaaa-aaaad-qemqq-cai.icp0.io/tag/au-supermarche/index.html | 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 |
|
Vulnerability description
We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Risk description
The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.
Recommendation
Ensure that all external resources the page references are loaded using HTTPS.
Classification
| CWE | CWE-319 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Twitter Ads | Advertising |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| Google Analytics GA4 | Analytics |
| imagesLoaded 4.1.4 | JavaScript libraries |
| jQuery 3.6.1 | JavaScript libraries |
| Masonry | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| Neve 3.4.5 | WordPress themes |
| Widgets | |
| WordPress 6.1.1 | CMS, Blogs |
| WordPress Block Editor | Page builders |
| ContentViews | Widgets, WordPress plugins |
| AddToAny | Widgets |
| Google Tag Manager | Tag managers |
| 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://75gkk-2iaaa-aaaad-qemqq-cai.icp0.io/tag/au-supermarche/index.html | 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: AbsurdieMiAmor@protonmail.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 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2024-31210 | 7.6 | 0.00994 | 0.77031 | No | WordPress is an open publishing platform for the Web. It's possible for a file of a type other than a zip file to be submitted as a new plugin by an administrative user on the Plugins -> Add New -> Upload Plugin screen in WordPress. If FTP credentials are requested for installation (in order to move the file into place outside of the `uploads` directory) then the uploaded file remains temporary available in the Media Library despite it not being allowed. If the `DISALLOW_FILE_EDIT` constant is set to `true` on the site _and_ FTP credentials are required when uploading a new theme or plugin, then this technically allows an RCE when the user would otherwise have no means of executing arbitrary PHP code. This issue _only_ affects Administrator level users on single site installations, and Super Admin level users on Multisite installations where it's otherwise expected that the user does not have permission to upload or execute arbitrary PHP code. Lower level users are not affected. Sites where the `DISALLOW_FILE_MODS` constant is set to `true` are not affected. Sites where an administrative user either does not need to enter FTP credentials or they have access to the valid FTP credentials, are not affected. The issue was fixed in WordPress 6.4.3 on January 30, 2024 and backported to versions 6.3.3, 6.2.4, 6.1.5, 6.0.7, 5.9.9, 5.8.9, 5.7.11, 5.6.13, 5.5.14, 5.4.15, 5.3.17, 5.2.20, 5.1.18, 5.0.21, 4.9.25, 2.8.24, 4.7.28, 4.6.28, 4.5.31, 4.4.32, 4.3.33, 4.2.37, and 4.1.40. A workaround is available. If the `DISALLOW_FILE_MODS` constant is defined as `true` then it will not be possible for any user to upload a plugin and therefore this issue will not be exploitable. |
| CVE-2024-4439 | 7.2 | 0.90817 | 0.99635 | No | WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in various versions up to 6.5.2 due to insufficient output escaping on the display name. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. In addition, it also makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that have the comment block present and display the comment author's avatar. |
| CVE-2023-38000 | 6.5 | 0.00347 | 0.57245 | No | Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions. |
| CVE-2022-3590 | 5.9 | 0.90761 | 0.9963 | No | WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden. |
| CVE-2023-2745 | 5.4 | 0.77175 | 0.98984 | No | WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack. |
Vulnerability description
Vulnerabilities found for WordPress 6.1.1
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We found insecure DNS cookie usage on the following nameservers: hassan.ns.cloudflare.com, lara.ns.cloudflare.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
We managed to detect that WordPress has reached the End-of-Life (EOL).
Version detected: 6.1.1 End-of-life date: 2023-03-29 Latest version for the cycle: 6.1.10 This release cycle (6.1) doesn't have long-term-support (LTS). The cycle was released on 2022-11-02 and its latest release date was 2026-03-12.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | A | IPv4 address | 212.71.124.188 |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | A | IPv4 address | 195.5.171.242 |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | NS | Name server | hassan.ns.cloudflare.com |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | NS | Name server | lara.ns.cloudflare.com |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | SOA | Start of Authority | hassan.ns.cloudflare.com. dns.cloudflare.com. 2402916568 10000 2400 604800 1800 |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:61ff:fe45:43ab |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | AAAA | IPv6 address | 2602:fb2b:110:1:bcfb:b8ff:fe09:c741 |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| 75gkk-2iaaa-aaaad-qemqq-cai.icp0.io | CNAME | Canonical name | boundary.dfinity.network |
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 |
|---|---|
| WordPress 6.1.1 | CMS, Blogs |
| WordPress Block Editor | Page builders |
| MySQL | Databases |
| PHP | Programming languages |
| Neve 3.4.5 | WordPress themes |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| Widgets | |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| jQuery | JavaScript libraries |
| imagesLoaded 4.1.4 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| AddToAny | Widgets |
| DoubleClick Floodlight | Advertising |
| 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.