The version of Next.js installed on the remote host is 13.5.1 prior to 13.5.7 or 14.0.x prior to 14.2.10. It is, therefore, affected by a Cache Poisoning.

Note that the scanner has not attempted to exploit this issue but has instead relied only on application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request,
    it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this
    does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a
    route that is meant to not be cached and send a `Cache-Control: s-maxage=1, stale-while-revalidate` header
    which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1.
    Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered
    routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx`. This vulnerability was resolved in Next.js
    v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or
    not. There are no official or recommended workarounds for this issue, we recommend that users patch to a
    safe version. (CVE-2024-46982)

ID	Name	Product	Family	Published	Updated	Severity
114770	Next.js 14.0.x < 14.2.10 Cache Poisoning	Web App Scanning	Component Vulnerability	4/10/2025	4/10/2025	high
114769	Next.js 13.5.1 < 13.5.7 Cache Poisoning	Web App Scanning	Component Vulnerability	4/10/2025	4/10/2025	high
415225	SCA: security update for next (GHSA-gp8f-8m3g-qvj9)	Tenable Self-Hosted Container Security	SCA Checks	1/23/2025	7/2/2026	high
415225	SCA: security update for next (GHSA-gp8f-8m3g-qvj9)	Tenable Cloud Security	SCA Checks	1/23/2025	7/2/2026	high

Detections

Analytics

Plugins Search

high

high

high

high