Vulnerability Scan Result
| Title: | Wet Glaze Finish Care - Premium Car Care Brand |
| Description: | Wet Glaze Finish Care, Seattle, Washington. Born from the legacy of Wet Glaze 2.0, Wet Glaze Finish Care delivers professional-grade car wash soaps, polishes, sealants, and detailing sprays. Premium formulas. Authentic performance. Unmistakable shine. |
| ip_address | 23.227.38.65 |
| country | CA  |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
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 | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| Facebook Pixel | Analytics |
| LazySizes | JavaScript libraries, Performance |
| core-js 2.6.12 | JavaScript libraries |
| Handlebars 4.0.3 | JavaScript frameworks |
| HTTP/3 | Miscellaneous |
| jQuery 2.2.3 | JavaScript libraries |
| Judge.me | Reviews |
| Open Graph | Miscellaneous |
| Amazon Pay | Payment processors |
| Google Pay | Payment processors |
| PayPal | Payment processors |
| Shop Pay | Payment processors |
| Shopify | Ecommerce |
| Priority Hints | Performance |
| American Express | Payment processors |
| Apple Pay | Payment processors |
| Cloudflare | CDN |
| Lodash 4.5.1 | JavaScript libraries |
| Mastercard | Payment processors |
| HSTS | Security |
| Visa | Payment processors |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2019-19919 | 9.8 | 0.17796 | 0.95059 | Versions of handlebars prior to 4.3.0 are vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Object's __proto__ and __defineGetter__ properties, which may allow an attacker to execute arbitrary code through crafted payloads. |
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
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2019-10744 | 9.1 | 0.03254 | 0.87014 | Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload. |
| CVE-2020-8203 | 7.4 | 0.02826 | 0.86028 | Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. |
| CVE-2021-23337 | 7.2 | 0.00517 | 0.66478 | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. |
| CVE-2025-13465 | 6.9 | 0.00028 | 0.07846 | Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23 |
| CVE-2019-1010266 | 6.5 | 0.00211 | 0.43476 | lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. |
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 | Cookie Name | Evidence |
|---|---|---|
| https://www.wetglazefinish.com/ | localization, cart_currency | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: localization=US Set-Cookie: cart_currency=USD |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.wetglazefinish.com/ | localization, cart_currency | Set-Cookie: localization=US Set-Cookie: cart_currency=USD |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.36851 | 0.97101 | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-11022 | 6.9 | 0.03251 | 0.87007 | In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2019-11358 | 6.1 | 0.02717 | 0.85781 | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
| CVE-2015-9251 | 6.1 | 0.27164 | 0.96333 | jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed. |
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://www.wetglazefinish.com/ | 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
| Software / Version | Category |
|---|---|
| Facebook Pixel | Analytics |
| LazySizes | JavaScript libraries, Performance |
| core-js 2.6.12 | JavaScript libraries |
| Handlebars 4.0.3 | JavaScript frameworks |
| HTTP/3 | Miscellaneous |
| jQuery 2.2.3 | JavaScript libraries |
| Judge.me | Reviews |
| Open Graph | Miscellaneous |
| Amazon Pay | Payment processors |
| Google Pay | Payment processors |
| PayPal | Payment processors |
| Shop Pay | Payment processors |
| Shopify | Ecommerce |
| Priority Hints | Performance |
| American Express | Payment processors |
| Apple Pay | Payment processors |
| Cloudflare | CDN |
| Lodash 4.5.1 | JavaScript libraries |
| Mastercard | Payment processors |
| HSTS | Security |
| Visa | Payment processors |
| Cart Functionality | Ecommerce |
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 | Evidence |
|---|---|
| https://www.wetglazefinish.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 |
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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.wetglazefinish.com/products/skinny-scrubber-gentle-leather-and-interior-sponge-6-pack | 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 Cookies: _shopify_essential=:AZ0W03vtAAEAHRiAFs4hmQEz5O45q91wAidD86hVe_ihDiaSZII1PcRNZr49C6GxS6M1dir9u3AsJZ7Hyoz8jGytGXeF7OwPSGzFL6DWx0FCDYnory6KBMBzQ2... |
|
| https://www.wetglazefinish.com/products/vehicle-deodorization-kit-car-odor-bomb | 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 Cookies: _shopify_essential=:AZ0W03vtAAEAHRiAFs4hmQEz5O45q91wAidD86hVe_ihDiaSZII1PcRNZr49C6GxS6M1dir9u3AsJZ7Hyoz8jGytGXeF7OwPSGzFL6DWx0FCDYnory6KBMBzQ2... |
|
| https://www.wetglazefinish.com/products/wet-glaze-ceramic-coat | 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 Cookies: _shopify_essential=:AZ0W03vtAAEAHRiAFs4hmQEz5O45q91wAidD86hVe_ihDiaSZII1PcRNZr49C6GxS6M1dir9u3AsJZ7Hyoz8jGytGXeF7OwPSGzFL6DWx0FCDYnory6KBMBzQ2... |
|
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 |
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 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.wetglazefinish.com/policies/terms-of-service | 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 Cookies: _shopify_essential=:AZ0W03vtAAEAHRiAFs4hmQEz5O45q91wAidD86hVe_ihDiaSZII1PcRNZr49C6GxS6M1dir9u3AsJZ7Hyoz8jGytGXeF7OwPSGzFL6DWx0FCDYnory6KBMBzQ2... | Email Address: sales@wetglazefinish.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
We found insecure DNS cookie usage on the following nameservers: ns1.bluehost.com, ns2.bluehost.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
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.wetglazefinish.com | A | IPv4 address | 23.227.38.65 |
| www.wetglazefinish.com | NS | Name server | ns1.bluehost.com |
| www.wetglazefinish.com | NS | Name server | ns2.bluehost.com |
| www.wetglazefinish.com | MX | Mail server | 0 mail.wetglazefinish.com |
| www.wetglazefinish.com | SOA | Start of Authority | ns1.bluehost.com. root.box5313.bluehost.com. 2023102600 86400 7200 3600000 300 |
| www.wetglazefinish.com | SPF | Sender Policy Framework | "v=spf1 a mx include:websitewelcome.com ~all" |
| www.wetglazefinish.com | CNAME | Canonical name | wetglazefinish.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 |
|---|---|
| Shopify | Ecommerce |
| Shop Pay | Payment processors |
| PayPal | Payment processors |
| Judge.me | Reviews |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 12.0-RELEASE | 92% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.