Vulnerability Scan Result
| Title: | Just a moment... |
| Description: | No description found |
| ip_address | 104.18.11.141 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.18.10.141 |
| 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 | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Microsoft Advertising | Advertising |
| Amplitude | Analytics |
| Google Sign-in | Authentication |
| Facebook Pixel | Analytics |
| Bootstrap 9 | UI frameworks |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| Moment.js | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Google Ads Conversion Tracking | Analytics |
| WooCommerce | Ecommerce, WordPress plugins |
| WordPress | CMS, Blogs |
| OnePress Social Locker | WordPress plugins |
| Algolia | Search engines |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| Google Tag Manager | Tag managers |
| Cart Functionality | Ecommerce |
| Yoast SEO 12.3 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Microsoft Advertising | Advertising |
| Amplitude | Analytics |
| Google Sign-in | Authentication |
| Facebook Pixel | Analytics |
| Bootstrap 9 | UI frameworks |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| Moment.js | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Google Ads Conversion Tracking | Analytics |
| WooCommerce | Ecommerce, WordPress plugins |
| WordPress | CMS, Blogs |
| OnePress Social Locker | WordPress plugins |
| Algolia | Search engines |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| Google Tag Manager | Tag managers |
| Cart Functionality | Ecommerce |
| Yoast SEO 12.3 | SEO, WordPress plugins |
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 | Evidence |
|---|---|
| https://www.creativefabrica.com/product/anti-social-moms-club-7/ | 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 | Evidence |
|---|---|
| https://www.creativefabrica.com/product/anti-social-moms-club-7/ | 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 |
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2019-20891 | 8.8 | 0.0013 | 0.32954 | No | WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via includes/admin/importers/class-wc-product-csv-importer-controller.php. |
| CVE-2025-5062 | 6.1 | 0.00395 | 0.59815 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2019-9168 | 6.1 | 0.00192 | 0.41176 | No | WooCommerce before 3.5.5 allows XSS via a Photoswipe caption. |
| CVE-2024-9944 | 5.3 | 0.00359 | 0.57576 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2020-29156 | 5.3 | 0.13078 | 0.93904 | No | The WooCommerce plugin before 4.7.0 for WordPress allows remote attackers to view the status of arbitrary orders via the order_id parameter in a fetch_order_status action. |
Vulnerability description
Vulnerabilities found for WooCommerce 3.5.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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2019-20891 | 8.8 | 0.0013 | 0.32954 | No | WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via includes/admin/importers/class-wc-product-csv-importer-controller.php. |
| CVE-2025-5062 | 6.1 | 0.00395 | 0.59815 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2019-9168 | 6.1 | 0.00192 | 0.41176 | No | WooCommerce before 3.5.5 allows XSS via a Photoswipe caption. |
| CVE-2024-9944 | 5.3 | 0.00359 | 0.57576 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2020-29156 | 5.3 | 0.13078 | 0.93904 | No | The WooCommerce plugin before 4.7.0 for WordPress allows remote attackers to view the status of arbitrary orders via the order_id parameter in a fetch_order_status action. |
Vulnerability description
Vulnerabilities found for WooCommerce 3.5.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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2019-20891 | 8.8 | 0.0013 | 0.32954 | No | WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via includes/admin/importers/class-wc-product-csv-importer-controller.php. |
| CVE-2025-5062 | 6.1 | 0.00395 | 0.59815 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2019-9168 | 6.1 | 0.00192 | 0.41176 | No | WooCommerce before 3.5.5 allows XSS via a Photoswipe caption. |
| CVE-2024-9944 | 5.3 | 0.00359 | 0.57576 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2020-29156 | 5.3 | 0.13078 | 0.93904 | No | The WooCommerce plugin before 4.7.0 for WordPress allows remote attackers to view the status of arbitrary orders via the order_id parameter in a fetch_order_status action. |
Vulnerability description
Vulnerabilities found for WooCommerce 3.5.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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2019-20891 | 8.8 | 0.0013 | 0.32954 | No | WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via includes/admin/importers/class-wc-product-csv-importer-controller.php. |
| CVE-2025-5062 | 6.1 | 0.00395 | 0.59815 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2019-9168 | 6.1 | 0.00192 | 0.41176 | No | WooCommerce before 3.5.5 allows XSS via a Photoswipe caption. |
| CVE-2024-9944 | 5.3 | 0.00359 | 0.57576 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2020-29156 | 5.3 | 0.13078 | 0.93904 | No | The WooCommerce plugin before 4.7.0 for WordPress allows remote attackers to view the status of arbitrary orders via the order_id parameter in a fetch_order_status action. |
Vulnerability description
Vulnerabilities found for WooCommerce 3.5.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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2019-20891 | 8.8 | 0.0013 | 0.32954 | No | WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via includes/admin/importers/class-wc-product-csv-importer-controller.php. |
| CVE-2025-5062 | 6.1 | 0.00395 | 0.59815 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2019-9168 | 6.1 | 0.00192 | 0.41176 | No | WooCommerce before 3.5.5 allows XSS via a Photoswipe caption. |
| CVE-2024-9944 | 5.3 | 0.00359 | 0.57576 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2020-29156 | 5.3 | 0.13078 | 0.93904 | No | The WooCommerce plugin before 4.7.0 for WordPress allows remote attackers to view the status of arbitrary orders via the order_id parameter in a fetch_order_status action. |
Vulnerability description
Vulnerabilities found for WooCommerce 3.5.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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Algolia | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Envoy | Reverse proxies |
| Google Sign-in | Authentication |
| Bootstrap 9 | UI frameworks |
| React | JavaScript frameworks |
| Amplitude | Analytics |
| Cloudflare | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Yoast SEO 12.3 | SEO, WordPress plugins |
| Google Ads | Advertising |
| Moment.js | JavaScript libraries |
| Microsoft Advertising | Advertising |
| jsDelivr | CDN |
| jQuery UI | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Ads Conversion Tracking | Analytics |
| Facebook Pixel 2.9.252 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Cloudflare Bot Management | Security |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| WooCommerce 3.5.1 | Ecommerce, WordPress plugins |
| MailChimp | Marketing automation, Email |
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 |
|---|---|
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Algolia | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Envoy | Reverse proxies |
| Google Sign-in | Authentication |
| Bootstrap 9 | UI frameworks |
| React | JavaScript frameworks |
| Amplitude | Analytics |
| Cloudflare | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Yoast SEO 12.3 | SEO, WordPress plugins |
| Google Ads | Advertising |
| Moment.js | JavaScript libraries |
| jsDelivr | CDN |
| jQuery UI | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Ads Conversion Tracking | Analytics |
| Facebook Pixel 2.9.252 | Analytics |
| Clipboard.js | JavaScript libraries |
| Microsoft Advertising | Advertising |
| Google Analytics GA4 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare Bot Management | Security |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| WooCommerce 3.5.1 | Ecommerce, WordPress plugins |
| MailChimp | Marketing automation, Email |
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.1-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.creativefabrica.com | A | IPv4 address | 104.18.11.141 |
| www.creativefabrica.com | A | IPv4 address | 104.18.10.141 |
| www.creativefabrica.com | AAAA | IPv6 address | 2606:4700::6812:a8d |
| www.creativefabrica.com | AAAA | IPv6 address | 2606:4700::6812:b8d |
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 | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Algolia | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Envoy | Reverse proxies |
| Google Sign-in | Authentication |
| Bootstrap 9 | UI frameworks |
| React | JavaScript frameworks |
| Amplitude | Analytics |
| Cloudflare | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Yoast SEO 12.3 | SEO, WordPress plugins |
| Google Ads | Advertising |
| Moment.js | JavaScript libraries |
| Microsoft Advertising | Advertising |
| jsDelivr | CDN |
| jQuery UI | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Ads Conversion Tracking | Analytics |
| Facebook Pixel 2.9.252 | Analytics |
| Clipboard.js | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare Bot Management | Security |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| WooCommerce 3.5.1 | Ecommerce, WordPress plugins |
| MailChimp | Marketing automation, Email |
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 |
|---|---|
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Algolia | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Envoy | Reverse proxies |
| Google Sign-in | Authentication |
| Bootstrap 9 | UI frameworks |
| React | JavaScript frameworks |
| Amplitude | Analytics |
| Cloudflare | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Yoast SEO 12.3 | SEO, WordPress plugins |
| Google Ads | Advertising |
| Moment.js | JavaScript libraries |
| Microsoft Advertising | Advertising |
| jsDelivr | CDN |
| jQuery UI | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Ads Conversion Tracking | Analytics |
| Facebook Pixel 2.9.252 | Analytics |
| Clipboard.js | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare Bot Management | Security |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| WooCommerce 3.5.1 | Ecommerce, WordPress plugins |
| MailChimp | Marketing automation, Email |
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 |
|---|---|
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Algolia | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Envoy | Reverse proxies |
| Google Sign-in | Authentication |
| Bootstrap 9 | UI frameworks |
| React | JavaScript frameworks |
| Amplitude | Analytics |
| Cloudflare | CDN |
| Webpack | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Yoast SEO 12.3 | SEO, WordPress plugins |
| Google Ads | Advertising |
| Moment.js | JavaScript libraries |
| Microsoft Advertising | Advertising |
| jsDelivr | CDN |
| jQuery UI | JavaScript libraries |
| jQuery Migrate 1.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Facebook Pixel 2.9.252 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Cloudflare Bot Management | Security |
| MailChimp for WooCommerce 2.1.11 | WordPress plugins |
| WooCommerce 3.5.1 | Ecommerce, WordPress plugins |
| MailChimp | Marketing automation, Email |
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.