Vulnerability Scan Result
| Title: | wsj.com |
| Description: | No description found |
| ip_address | 99.86.91.5 |
| country | US  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 99.86.91.7 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 99.86.91.99 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 99.86.91.25 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Amazon Advertising | Advertising |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Amazon S3 | CDN |
| DataDome | Security |
| Google Publisher Tag | Advertising |
| Emotion | JavaScript frameworks, Development |
| core-js 3.47.0 | JavaScript libraries |
| Integral Ad Science | Advertising |
| New Relic | RUM |
| Next.js 14.2.26 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Prebid 10.25.0 | Advertising |
| React 18.3.1 | JavaScript frameworks |
| styled-components 5.3.11 | JavaScript frameworks, Development |
| DoubleClick Floodlight | Advertising |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| Ad Lightning | Advertising |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-44578 | 8.6 | 0.02829 | 0.84759 | 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.00351 | 0.2682 | 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.1888 | 0.96925 | 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.65592 | 0.99165 | 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.00683 | 0.47614 | 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
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
| Software / Version | Category |
|---|---|
| Amazon Advertising | Advertising |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Amazon S3 | CDN |
| DataDome | Security |
| Google Publisher Tag | Advertising |
| Emotion | JavaScript frameworks, Development |
| core-js 3.47.0 | JavaScript libraries |
| Integral Ad Science | Advertising |
| New Relic | RUM |
| Next.js 14.2.26 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Prebid 10.25.0 | Advertising |
| React 18.3.1 | JavaScript frameworks |
| styled-components 5.3.11 | JavaScript frameworks, Development |
| DoubleClick Floodlight | Advertising |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| Ad Lightning | Advertising |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
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 |
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon S3 | CDN |
| DataDome | Security |
| Amazon CloudFront | CDN |
| Integral Ad Science | Advertising |
| Google Publisher Tag | Advertising |
| DoubleClick Floodlight | Advertising |
| Ad Lightning | Advertising |
| reCAPTCHA | Security |
| Amazon Advertising | Advertising |
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
| Software / Version | Category |
|---|---|
| Cart Functionality | Ecommerce |
| styled-components 5.3.11 | JavaScript frameworks, Development |
| Emotion | JavaScript frameworks, Development |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| Amazon Advertising | Advertising |
| Amazon S3 | CDN |
| DataDome | Security |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Integral Ad Science | Advertising |
| Google Publisher Tag | Advertising |
| DoubleClick Floodlight | Advertising |
| Ad Lightning | Advertising |
| reCAPTCHA | Security |
| Priority Hints | Performance |
| DoubleVerify | Advertising, Analytics |
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 |
|---|---|---|---|
| deloitte.wsj.com | A | IPv4 address | 99.86.91.25 |
| deloitte.wsj.com | A | IPv4 address | 99.86.91.99 |
| deloitte.wsj.com | A | IPv4 address | 99.86.91.7 |
| deloitte.wsj.com | A | IPv4 address | 99.86.91.5 |
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.