Vulnerability Scan Result
| Title: | SunPower – Powering a Brighter Future | SunPower® |
| Description: | We provide residential solar, battery storage, and custom solutions for homes, built to last with quality and backed by decades of solar expertise. |
| ip_address | 99.86.91.65 |
| country | US  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 99.86.91.67 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 99.86.91.117 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 99.86.91.2 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| GraphQL | Programming languages |
| lit-element 4.2.2 | JavaScript libraries |
| Google Maps | Maps |
| MySQL | Databases |
| Next.js 14.2.28 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| PHP | Programming languages |
| React | JavaScript frameworks |
| DoubleClick Floodlight | Advertising |
| Swiper | JavaScript libraries |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Algolia | Search engines |
| Apollo 3.13.7 | JavaScript libraries |
| Contentful | CMS |
| Datadog | RUM, Analytics |
| Google Tag Manager | Tag managers |
| OneTrust | Cookie compliance |
| HSTS | Security |
| TypeScript | Programming languages |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-44578 | 8.6 | 0.00032 | 0.09306 | 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-44573 | 7.5 | 0.00038 | 0.11321 | Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2025-67779 | 7.5 | 0.00448 | 0.63712 | It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. |
| CVE-2025-55184 | 7.5 | 0.38423 | 0.97285 | A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. |
| CVE-2026-27980 | 6.9 | 0.00022 | 0.06457 | Next.js is a React framework for building full-stack web applications. Starting in version 10.0.0 and prior to version 16.1.7, the default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth. An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. This is fixed in version 16.1.7 by adding an LRU-backed disk cache with `images.maximumDiskCacheSize`, including eviction of least-recently-used entries when the limit is exceeded. Setting `maximumDiskCacheSize: 0` disables disk caching. If upgrading is not immediately possible, periodically clean `.next/cache/images` and/or reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`). |
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://us.sunpower.com/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
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://us.sunpower.com/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://us.sunpower.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 |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| GraphQL | Programming languages |
| lit-element 4.2.2 | JavaScript libraries |
| Google Maps | Maps |
| MySQL | Databases |
| Next.js 14.2.28 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| PHP | Programming languages |
| React | JavaScript frameworks |
| DoubleClick Floodlight | Advertising |
| Swiper | JavaScript libraries |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Algolia | Search engines |
| Apollo 3.13.7 | JavaScript libraries |
| Contentful | CMS |
| Datadog | RUM, Analytics |
| Google Tag Manager | Tag managers |
| OneTrust | Cookie compliance |
| HSTS | Security |
| TypeScript | Programming languages |
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 |
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://us.sunpower.com/trademarks | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: trademarks@sunpower.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 EDNS configuration on the following nameservers: ns-1126.awsdns-12.org, ns-1893.awsdns-44.co.uk, ns-968.awsdns-57.net ns-1126.awsdns-12.org:
ns-1893.awsdns-44.co.uk:
ns-968.awsdns-57.net:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-1126.awsdns-12.org, ns-1893.awsdns-44.co.uk, ns-352.awsdns-44.com, ns-968.awsdns-57.net
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 |
|---|---|
| Contentful | CMS |
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Algolia | Search engines |
| MySQL | Databases |
| PHP | Programming languages |
| Google Maps | Maps |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| OneTrust | Cookie compliance |
| Google Tag Manager | Tag managers |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Webpack | 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 |
|---|---|
| Crestron XPanel control system | 87% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| us.sunpower.com | A | IPv4 address | 99.86.91.65 |
| us.sunpower.com | A | IPv4 address | 99.86.91.117 |
| us.sunpower.com | A | IPv4 address | 99.86.91.2 |
| us.sunpower.com | A | IPv4 address | 99.86.91.67 |
| us.sunpower.com | NS | Name server | ns-1126.awsdns-12.org |
| us.sunpower.com | NS | Name server | ns-1893.awsdns-44.co.uk |
| us.sunpower.com | NS | Name server | ns-352.awsdns-44.com |
| us.sunpower.com | NS | Name server | ns-968.awsdns-57.net |
| us.sunpower.com | SOA | Start of Authority | ns-352.awsdns-44.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:c200:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:2000:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:7800:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:1e00:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:ac00:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:fc00:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:8800:15:247:9080:93a1 |
| us.sunpower.com | AAAA | IPv6 address | 2600:9000:2117:9c00:15:247:9080:93a1 |
| us.sunpower.com | CNAME | Canonical name | d3koexpi4gbeiq.cloudfront.net |
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.