Vulnerability Scan Result
| Title: | Just a moment... |
| Description: | No description found |
| ip_address | 172.66.170.72 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.20.27.147 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
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 | https-alt | cloudflare - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| TikTok Pixel | Analytics |
| Reddit Ads | Advertising |
| Aplazame | Payment processors, Buy now pay later |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Trustpilot | Reviews |
| Matomo Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Bootstrap 5 | UI frameworks |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| HTTP/3 | Miscellaneous |
| lit-element 4.2.2 | JavaScript libraries |
| Magento | Ecommerce |
| MySQL | Databases |
| Next.js 15.5.9 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Next.js App Router | JavaScript frameworks, Web servers |
| PHP | Programming languages |
| Piwik PRO Core | Analytics |
| React | JavaScript frameworks |
| Strapi | CMS |
| DoubleClick Floodlight | Advertising |
| Google Ads Conversion Tracking | Analytics |
| Svelte | JavaScript frameworks |
| Typesense | Search engines |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| CookieHub | Cookie compliance |
| e-goi | Marketing automation, Email |
| Google Tag Manager | Tag managers |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| SeQura | Buy now pay later |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-44578 | 8.6 | 0.37756 | 0.98348 | Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44574 | 8.1 | 0.00383 | 0.29998 | Next.js is a React framework for building full-stack web applications. From 15.4.0 to before 15.5.16 and 16.2.5, applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-45109 | 7.5 | 0.00386 | 0.30279 | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.18 and 16.2.6, it was found that the fix addressing CVE-2026-44575 did not apply to middleware.ts with Turbopack. This vulnerability is fixed in 15.5.18 and 16.2.6. |
| CVE-2026-44579 | 7.5 | 0.00461 | 0.36518 | Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44575 | 7.5 | 0.01048 | 0.59811 | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.16 and 16.2.5, App Router applications that rely on middleware or proxy-based checks for authorization can allow unauthorized access through transport-specific route variants used for segment prefetching. In affected configurations, specially crafted .rsc and segment-prefetch URLs can resolve to the same page without being matched by the intended middleware rule, which can allow protected content to be reached without the expected authorization check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
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
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| TikTok Pixel | Analytics |
| Reddit Ads | Advertising |
| Aplazame | Payment processors, Buy now pay later |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Trustpilot | Reviews |
| Matomo Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Bootstrap 5 | UI frameworks |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| HTTP/3 | Miscellaneous |
| lit-element 4.2.2 | JavaScript libraries |
| Magento | Ecommerce |
| MySQL | Databases |
| Next.js 15.5.9 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Next.js App Router | JavaScript frameworks, Web servers |
| PHP | Programming languages |
| Piwik PRO Core | Analytics |
| React | JavaScript frameworks |
| Strapi | CMS |
| DoubleClick Floodlight | Advertising |
| Google Ads Conversion Tracking | Analytics |
| Svelte | JavaScript frameworks |
| Typesense | Search engines |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| CookieHub | Cookie compliance |
| e-goi | Marketing automation, Email |
| Google Tag Manager | Tag managers |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| SeQura | Buy now pay later |
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
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://pcdiga.com/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2026-44578 | 8.6 | 0.37756 | 0.98348 | No | Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44574 | 8.1 | 0.00383 | 0.29998 | No | Next.js is a React framework for building full-stack web applications. From 15.4.0 to before 15.5.16 and 16.2.5, applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-45109 | 7.5 | 0.00386 | 0.30279 | No | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.18 and 16.2.6, it was found that the fix addressing CVE-2026-44575 did not apply to middleware.ts with Turbopack. This vulnerability is fixed in 15.5.18 and 16.2.6. |
| CVE-2026-44579 | 7.5 | 0.00461 | 0.36518 | No | Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44575 | 7.5 | 0.01048 | 0.59811 | No | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.16 and 16.2.5, App Router applications that rely on middleware or proxy-based checks for authorization can allow unauthorized access through transport-specific route variants used for segment prefetching. In affected configurations, specially crafted .rsc and segment-prefetch URLs can resolve to the same page without being matched by the intended middleware rule, which can allow protected content to be reached without the expected authorization check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
Vulnerability description
Vulnerabilities found for Next.js 15.5.9
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2026-44578 | 8.6 | 0.37756 | 0.98348 | No | Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44574 | 8.1 | 0.00383 | 0.29998 | No | Next.js is a React framework for building full-stack web applications. From 15.4.0 to before 15.5.16 and 16.2.5, applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-45109 | 7.5 | 0.00386 | 0.30279 | No | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.18 and 16.2.6, it was found that the fix addressing CVE-2026-44575 did not apply to middleware.ts with Turbopack. This vulnerability is fixed in 15.5.18 and 16.2.6. |
| CVE-2026-44579 | 7.5 | 0.00461 | 0.36518 | No | Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44575 | 7.5 | 0.01048 | 0.59811 | No | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.16 and 16.2.5, App Router applications that rely on middleware or proxy-based checks for authorization can allow unauthorized access through transport-specific route variants used for segment prefetching. In affected configurations, specially crafted .rsc and segment-prefetch URLs can resolve to the same page without being matched by the intended middleware rule, which can allow protected content to be reached without the expected authorization check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
Vulnerability description
Vulnerabilities found for Next.js 15.5.9
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2026-44578 | 8.6 | 0.37756 | 0.98348 | No | Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44574 | 8.1 | 0.00383 | 0.29998 | No | Next.js is a React framework for building full-stack web applications. From 15.4.0 to before 15.5.16 and 16.2.5, applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-45109 | 7.5 | 0.00386 | 0.30279 | No | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.18 and 16.2.6, it was found that the fix addressing CVE-2026-44575 did not apply to middleware.ts with Turbopack. This vulnerability is fixed in 15.5.18 and 16.2.6. |
| CVE-2026-44579 | 7.5 | 0.00461 | 0.36518 | No | Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2026-44575 | 7.5 | 0.01048 | 0.59811 | No | Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.16 and 16.2.5, App Router applications that rely on middleware or proxy-based checks for authorization can allow unauthorized access through transport-specific route variants used for segment prefetching. In affected configurations, specially crafted .rsc and segment-prefetch URLs can resolve to the same page without being matched by the intended middleware rule, which can allow protected content to be reached without the expected authorization check. This vulnerability is fixed in 15.5.16 and 16.2.5. |
Vulnerability description
Vulnerabilities found for Next.js 15.5.9
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| zendesk1 | rsa | 912 | "v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9" "NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB" |
Vulnerability description
We found that the DKIM key length is under 1024-bit. When a DKIM (DomainKeys Identified Mail) key length is under 1024-bit, it is considered weak by modern cryptographic standards. Shorter key lengths, such as 512 or 768 bits, are vulnerable to brute-force attacks, where an attacker could potentially forge a valid DKIM signature for a domain. This undermines the entire purpose of DKIM, which is to authenticate email messages and prevent email spoofing by verifying that the message headers have not been tampered with. A DKIM key under 1024 bits significantly reduces the difficulty for attackers to break the signature.
Risk description
The primary risk of using a DKIM key with fewer than 1024 bits is that it weakens the domain's email authentication security, making it more susceptible to brute-force attacks. If an attacker successfully forges a DKIM signature, they can impersonate legitimate senders and send fraudulent or phishing emails that appear authentic to the recipient. This can lead to financial losses, reputational damage, and an increased risk of targeted attacks, as recipients are more likely to trust emails that pass DKIM verification.
Recommendation
We recommend using a DKIM key with a length of at least 1024 bits. Ideally, 2048-bit keys should be used, as they provide a higher level of security and are more resistant to brute-force attacks. Organizations should regularly audit their DKIM configurations and rotate cryptographic keys periodically to maintain security. In addition, any DKIM keys that are less than 1024 bits should be immediately replaced with stronger keys to prevent exploitation.
Evidence
We found insecure DNS cookie usage on the following nameservers: aida.ns.cloudflare.com, carter.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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoc47wn3zpoRPXJ6w8+8EZBtkPhHcxWHDk/OLfTVANcEcDW6NpBlI+K6RWs1gebPBPRy+K3TJ/tJ+phpKz5fvDwzLK/nLhck25SZonWMRUkKEN8uyBlGlF2Ev2TkouS7C/0pEtZkv9znlk/2W/BTRaer0AKEFwN/ZNXRLMbP2FvzrFi+s1l55k8+GypcxdpFpW" "\" \"pR/nIBZnm70tEapo9Ja1a8yHczeWuggMFW+vYe64Z8Tfz3tr5yVDOTUm2H01OqW+saad9Z/GvvpoNR//xmpUluF2m+/+No5C9CEdm4tUDWDbbDResBNCyjug4lpmsvtcb2FC90/S7tLyPAZhtNC8wIDAQAB;" |
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoc47wn3zpoRPXJ6w8+8EZBtkPhHcxWHDk/OLfTVANcEcDW6NpBlI+K6RWs1gebPBPRy+K3TJ/tJ+phpKz5fvDwzLK/nLhck25SZonWMRUkKEN8uyBlGlF2Ev2TkouS7C/0pEtZkv9znlk/2W/BTRaer0AKEFwN/ZNXRLMbP2FvzrFi+s1l55k8+GypcxdpFpW" "pR/nIBZnm70tEapo9Ja1a8yHczeWuggMFW+vYe64Z8Tfz3tr5yVDOTUm2H01OqW+saad9Z/GvvpoNR//xmpUluF2m+/+No5C9CEdm4tUDWDbbDResBNCyjug4lpmsvtcb2FC90/S7tLyPAZhtNC8wIDAQAB;" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pcdiga.com | TXT | Text record | "v=DMARC1; p=none; rua=mailto:dmarc@pcdiga.com" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pcdiga.com | TXT | Text record | "v=DMARC1; p=none; rua=mailto:dmarc@pcdiga.com" |
Vulnerability description
We found that the target uses p=none in the DMARC policy. The DMARC policy set to p=none means that the domain owner is not taking any action on emails that fail DMARC validation. This configuration effectively disables enforcement, allowing potentially spoofed or fraudulent emails to be delivered without any additional scrutiny.
Risk description
Emails that fail DMARC checks are still delivered to recipients. This leaves the domain highly vulnerable to email spoofing and phishing attacks, as malicious actors can impersonate the domain without facing any consequences from DMARC enforcement.
Recommendation
We recommend changing the DMARC policy to p=quarantine or, ideally, p=reject to actively block or quarantine emails that fail DMARC validation. This will enhance the security of your domain against spoofing and phishing attacks by ensuring that only legitimate emails are delivered.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pcdiga.com | TXT | Text record | "v=DMARC1; p=none; rua=mailto:dmarc@pcdiga.com" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
| Software / Version | Category |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js 15.5.9 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Reddit Ads | Advertising |
| Cloudflare Browser Insights | Analytics, RUM |
| Trustpilot | Reviews |
| TikTok Pixel | Analytics |
| SeQura | Buy now pay later |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
| Aplazame | Payment processors, Buy now pay later |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Piwik PRO Core | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Priority Hints | Performance |
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 |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Trustpilot | Reviews |
| SeQura | Buy now pay later |
| Reddit Ads | Advertising |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Aplazame | Payment processors, Buy now pay later |
| Piwik PRO Core | Analytics |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| TikTok Pixel | Analytics |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
| Priority Hints | Performance |
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 |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Trustpilot | Reviews |
| SeQura | Buy now pay later |
| Reddit Ads | Advertising |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Aplazame | Payment processors, Buy now pay later |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Piwik PRO Core | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| TikTok Pixel | Analytics |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
| Priority Hints | Performance |
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 |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js 15.5.9 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Reddit Ads | Advertising |
| Cloudflare Browser Insights | Analytics, RUM |
| Trustpilot | Reviews |
| TikTok Pixel | Analytics |
| SeQura | Buy now pay later |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
| Aplazame | Payment processors, Buy now pay later |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Piwik PRO Core | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Priority Hints | Performance |
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoc47wn3zpoRPXJ6w8+8EZBtkPhHcxWHDk/OLfTVANcEcDW6NpBlI+K6RWs1gebPBPRy+K3TJ/tJ+phpKz5fvDwzLK/nLhck25SZonWMRUkKEN8uyBlGlF2Ev2TkouS7C/0pEtZkv9znlk/2W/BTRaer0AKEFwN/ZNXRLMbP2FvzrFi+s1l55k8+GypcxdpFpW" "\" \"pR/nIBZnm70tEapo9Ja1a8yHczeWuggMFW+vYe64Z8Tfz3tr5yVDOTUm2H01OqW+saad9Z/GvvpoNR//xmpUluF2m+/+No5C9CEdm4tUDWDbbDResBNCyjug4lpmsvtcb2FC90/S7tLyPAZhtNC8wIDAQAB;" |
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoc47wn3zpoRPXJ6w8+8EZBtkPhHcxWHDk/OLfTVANcEcDW6NpBlI+K6RWs1gebPBPRy+K3TJ/tJ+phpKz5fvDwzLK/nLhck25SZonWMRUkKEN8uyBlGlF2Ev2TkouS7C/0pEtZkv9znlk/2W/BTRaer0AKEFwN/ZNXRLMbP2FvzrFi+s1l55k8+GypcxdpFpW" "pR/nIBZnm70tEapo9Ja1a8yHczeWuggMFW+vYe64Z8Tfz3tr5yVDOTUm2H01OqW+saad9Z/GvvpoNR//xmpUluF2m+/+No5C9CEdm4tUDWDbbDResBNCyjug4lpmsvtcb2FC90/S7tLyPAZhtNC8wIDAQAB;" |
| k1 | rsa | 1296 | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;" |
| selector1 | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCYimV7BaN3E8C/zBdgwblACR74caxn8fOBN1K2ajPV2nweuihobiGWRdocgoPO+U0ZEXCh1AqyejXpyJOzZgZq/vog1dlt/EAIXpRYaO4OpOE4Vp79G8wlZs6XSFfnJBe5GsNVivZro5sU6nzc5nkCePqlmynuKr+p22CTm3wgFwIDAQAB; n=1024,1450909238,1" "466720438" |
| zendesk1 | rsa | 912 | "v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9" "NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Trustpilot | Reviews |
| SeQura | Buy now pay later |
| Reddit Ads | Advertising |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Aplazame | Payment processors, Buy now pay later |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| Piwik PRO Core | Analytics |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| Open Graph | Miscellaneous |
| HTTP/3 | Miscellaneous |
| TikTok Pixel | Analytics |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Trustpilot | Reviews |
| SeQura | Buy now pay later |
| Reddit Ads | Advertising |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Aplazame | Payment processors, Buy now pay later |
| Piwik PRO Core | Analytics |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| TikTok Pixel | Analytics |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
| Priority Hints | Performance |
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 |
|---|---|---|---|
| pcdiga.com | SPF | Sender Policy Framework | "v=spf1 a mx include:spf.protection.outlook.com include:servers.mcsv.net include:amazonses.com include:mail.zendesk.com include:trustpilotservice.com include:_spf.kmitd.com -all" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| pcdiga.com | A | IPv4 address | 104.20.27.147 |
| pcdiga.com | A | IPv4 address | 172.66.170.72 |
| pcdiga.com | NS | Name server | aida.ns.cloudflare.com |
| pcdiga.com | NS | Name server | carter.ns.cloudflare.com |
| pcdiga.com | MX | Mail server | 0 pcdiga-com.mail.protection.outlook.com |
| pcdiga.com | SOA | Start of Authority | aida.ns.cloudflare.com. dns.cloudflare.com. 2407780803 10000 2400 604800 1800 |
| pcdiga.com | AAAA | IPv6 address | 2606:4700:10::ac42:aa48 |
| pcdiga.com | AAAA | IPv6 address | 2606:4700:10::6814:1b93 |
| pcdiga.com | TXT | Text record | "_globalsign-domain-verification=vfgVwbzBy4HxysnIMXDR_EwZSx6IfC8KVglT6IFv-4" |
| pcdiga.com | TXT | Text record | "anthropic-domain-verification-t241z7=WXCxGz1EJlE6U8oVhelyGulb1" |
| pcdiga.com | TXT | Text record | "facebook-domain-verification=ed223u1mgxa7zz0qixk165f603s833" |
| pcdiga.com | TXT | Text record | "google-site-verification=AcY2J6E3cGUadAx96R9xDHBRW4dyaClF30j8JVMeyzw" |
| pcdiga.com | TXT | Text record | "google-site-verification=_unlVaBCP-j3rD7KTnfWLFSaUiDv7bWkNdaUTelB0Q8" |
| pcdiga.com | TXT | Text record | "google-site-verification=w6h78157-TcFhONJzzYjZsF94HaUoFQeHm3oBhza1ao" |
| pcdiga.com | TXT | Text record | "openai-domain-verification=dv-haY1AytfFT7XJ7VFWlaipLrC" |
| pcdiga.com | SPF | Sender Policy Framework | "v=spf1 a mx include:spf.protection.outlook.com include:servers.mcsv.net include:amazonses.com include:mail.zendesk.com include:trustpilotservice.com include:_spf.kmitd.com -all" |
| _dmarc.pcdiga.com | TXT | Text record | "v=DMARC1; p=none; rua=mailto:dmarc@pcdiga.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.
Evidence
| Software / Version | Category |
|---|---|
| Strapi | CMS |
| Magento | Ecommerce |
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| Google Ads | Advertising |
| Trustpilot | Reviews |
| SeQura | Buy now pay later |
| Reddit Ads | Advertising |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Aplazame | Payment processors, Buy now pay later |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| Piwik PRO Core | Analytics |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| Open Graph | Miscellaneous |
| HTTP/3 | Miscellaneous |
| TikTok Pixel | Analytics |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
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 |
|---|---|
| Magento | Ecommerce |
| Strapi | CMS |
| WordPress | CMS, Blogs |
| Next.js 15.5.9 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Typesense | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| AngularJS | JavaScript frameworks |
| Svelte | JavaScript frameworks |
| Next.js App Router | JavaScript frameworks, Web servers |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Google Ads | Advertising |
| Cloudflare Turnstile | Security |
| TikTok Pixel | Analytics |
| Matomo Tag Manager | Tag managers |
| lit-html 3.3.3 | JavaScript libraries |
| lit-element 4.2.2 | JavaScript libraries |
| e-goi | Marketing automation, Email |
| core-js 3.32.2 | JavaScript libraries |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| Trustpilot | Reviews |
| SeQura | Buy now pay later |
| Reddit Ads | Advertising |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.345 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Aplazame | Payment processors, Buy now pay later |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Piwik PRO Core | Analytics |
| DoubleClick Floodlight | Advertising |
| Klarna Checkout | Payment processors, Buy now pay later |
| HSTS | Security |
| CookieHub | Cookie compliance |
| Cloudflare | CDN |
| Amazon S3 | CDN |
| Webpack | Miscellaneous |
| Open Graph | Miscellaneous |
| 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.