Vulnerability Scan Result
| Title: | TrialSiteNews | Independent Censorship-Free Media for Health & Biomedical Research |
| Description: | Transparent coverage of clinical research |
| ip_address | 66.33.60.67 |
| country | US  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 76.76.21.98 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | Vercel - |
443/tcp | https | Vercel - |
| Software / Version | Category |
|---|---|
| Google Sign-in | Authentication |
| Emotion | JavaScript frameworks, Development |
| Google Font API | Font scripts |
| core-js 3.0.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Material UI | UI frameworks |
| MySQL | Databases |
| Next.js 15.3.8 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Sentry | Issue trackers |
| Stripe | Payment processors |
| styled-components 5.3.11 | JavaScript frameworks, Development |
| DoubleClick Floodlight | Advertising |
| Vercel | PaaS |
| Webpack | Miscellaneous |
| WordPress | CMS, Blogs |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HubSpot | Marketing automation |
| HubSpot Chat | Live chat |
| HubSpot Analytics | Analytics |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-27980 | 6.9 | 0.00022 | 0.06439 | 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`). |
| CVE-2026-29057 | 6.3 | 0.00031 | 0.09136 | Next.js is a React framework for building full-stack web applications. Starting in version 9.5.0 and prior to versions 15.5.13 and 16.1.7, when Next.js rewrites proxy traffic to an external backend, a crafted `DELETE`/`OPTIONS` request using `Transfer-Encoding: chunked` could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes. An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel. The vulnerability originated in an upstream library vendored by Next.js. It is fixed in Next.js 15.5.13 and 16.1.7 by updating that dependency’s behavior so `content-length: 0` is added only when both `content-length` and `transfer-encoding` are absent, and `transfer-encoding` is no longer removed in that code path. If upgrading is not immediately possible, block chunked `DELETE`/`OPTIONS` requests on rewritten routes at the edge/proxy, and/or enforce authentication/authorization on backend routes. |
| CVE-2025-59472 | 5.9 | 0.00089 | 0.25171 | A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the `Next-Resume: 1` header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion: 1. **Unbounded request body buffering**: The server buffers the entire POST request body into memory using `Buffer.concat()` without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory. 2. **Unbounded decompression (zipbomb)**: The resume data cache is decompressed using `inflateSync()` without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion. Both attack vectors result in a fatal V8 out-of-memory error (`FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server. To be affected you must have an application running with `experimental.ppr: true` or `cacheComponents: true` configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable. Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications. |
| CVE-2025-59471 | 5.9 | 0.00027 | 0.0788 | A denial of service vulnerability exists in self-hosted Next.js applications that have `remotePatterns` configured for the Image Optimizer. The image optimization endpoint (`/_next/image`) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that `remotePatterns` is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain. Strongly consider upgrading to 15.5.10 or 16.1.5 to reduce risk and prevent availability issues in Next applications. |
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.trialsitenews.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://www.trialsitenews.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
| Software / Version | Category |
|---|---|
| Google Sign-in | Authentication |
| Emotion | JavaScript frameworks, Development |
| Google Font API | Font scripts |
| core-js 3.0.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Material UI | UI frameworks |
| MySQL | Databases |
| Next.js 15.3.8 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Sentry | Issue trackers |
| Stripe | Payment processors |
| styled-components 5.3.11 | JavaScript frameworks, Development |
| DoubleClick Floodlight | Advertising |
| Vercel | PaaS |
| Webpack | Miscellaneous |
| WordPress | CMS, Blogs |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HubSpot | Marketing automation |
| HubSpot Chat | Live chat |
| HubSpot Analytics | Analytics |
| HSTS | Security |
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.trialsitenews.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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.trialsitenews.com/about-us | 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: tips@trialsitenews.com help@trialsitenews.com |
| https://www.trialsitenews.com/contact-us | 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: info@trialsitenews.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 |
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
We found insecure DNS cookie usage on the following nameservers: deb.ns.cloudflare.com, quinton.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
| Operating System | Accuracy |
|---|---|
| Android 5.0.1 | 87% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.trialsitenews.com | A | IPv4 address | 76.76.21.241 |
| www.trialsitenews.com | A | IPv4 address | 66.33.60.193 |
| www.trialsitenews.com | NS | Name server | deb.ns.cloudflare.com |
| www.trialsitenews.com | NS | Name server | quinton.ns.cloudflare.com |
| www.trialsitenews.com | MX | Mail server | 10 mx1.emailsrvr.com |
| www.trialsitenews.com | MX | Mail server | 20 mx2.emailsrvr.com |
| www.trialsitenews.com | SOA | Start of Authority | deb.ns.cloudflare.com. dns.cloudflare.com. 2402473105 10000 2400 604800 1800 |
| www.trialsitenews.com | TXT | Text record | "NETORGFT4039374.onmicrosoft.com" |
| www.trialsitenews.com | TXT | Text record | "google-site-verification=hGZBMG9-_7EpN3i0Q-d5a0Izk5EQvr_FYlUnSxy9oKE" |
| www.trialsitenews.com | SPF | Sender Policy Framework | "v=spf1 include:emailsrvr.com ~all" |
| www.trialsitenews.com | CAA | Certificate Authority Authorization | 0 issue "globalsign.com" |
| www.trialsitenews.com | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| www.trialsitenews.com | CAA | Certificate Authority Authorization | 0 issue "pki.goog" |
| www.trialsitenews.com | CAA | Certificate Authority Authorization | 0 issue "sectigo.com" |
| www.trialsitenews.com | CNAME | Canonical name | trialsitenews.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 |
|---|---|
| WordPress | CMS, Blogs |
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| MySQL | Databases |
| PHP | Programming languages |
| Google Sign-in | Authentication |
| Material UI | UI frameworks |
| React | JavaScript frameworks |
| Stripe | Payment processors |
| Vercel | PaaS |
| HubSpot Chat | Live chat |
| HubSpot Analytics | Analytics |
| HubSpot | Marketing automation |
| Google Tag Manager | Tag managers |
| reCAPTCHA | Security |
| DoubleClick Floodlight | Advertising |
| Google Analytics GA4 | Analytics |
| HSTS | Security |
| 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.