Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-92931 Overview
CVE-2026-92931 is a Server-Side Request Forgery (SSRF) vulnerability [CWE-918] in the Progress @progress/sitefinity-nextjs-sdk npm package. The flaw affects versions 15.1.8326 through 15.4.8637 and allows a remote attacker to coerce the server into issuing HTTP requests to attacker-controlled destinations. Successful exploitation can expose sensitive information, including internal service responses, cloud metadata, and credentials reachable from the application host.
Critical Impact
Unauthenticated attackers can trigger server-side HTTP requests to arbitrary hosts, exposing internal services and sensitive data when a user interacts with a crafted link.
Affected Products
- Progress @progress/sitefinity-nextjs-sdk npm package version 15.1.8326
- Progress @progress/sitefinity-nextjs-sdk npm package versions 15.2.x and 15.3.x
- Progress @progress/sitefinity-nextjs-sdk npm package versions up to and including 15.4.8637
Discovery Timeline
- 2026-10-05 - CVE-2026-92931 published to the National Vulnerability Database (NVD)
- 2026-10-06 - CVE-2026-92931 last updated in the NVD database
Technical Details for CVE-2026-92931
Vulnerability Analysis
The vulnerability resides in request-handling logic within the Sitefinity Next.js SDK, where a user-controlled URL or host parameter is passed to a server-side fetch routine without sufficient validation. Because the SDK executes the resulting request from the Next.js server runtime, the attacker gains the ability to reach systems reachable by that runtime, including internal subnets, management endpoints, and cloud instance metadata services.
The attack requires user interaction, typically clicking a crafted link or visiting an attacker-controlled page that triggers the vulnerable endpoint. Once the request is proxied, the response or side effects can be observed by the attacker, leaking data that was never intended to leave the trust boundary.
Root Cause
The root cause is insufficient allowlisting and URL validation on server-side request parameters within the SDK. Request destinations derived from HTTP input are forwarded to outbound HTTP clients without constraining the scheme, host, or network scope.
Attack Vector
Exploitation occurs over the network against the Next.js server hosting the SDK. The attacker crafts a request or link that encodes an internal or attacker-controlled URL as input. When the server processes the request, it issues an outbound call to that URL and may return the response to the attacker. Refer to the Progress Sitefinity Security Advisory for vendor-provided technical details.
Detection Methods for CVE-2026-92931
Indicators of Compromise
- Outbound HTTP requests from the Next.js application server to internal RFC1918 addresses, link-local metadata endpoints such as 169.254.169.254, or unexpected external hosts.
- Access log entries containing suspicious URL parameters referencing http://, https://, file://, or gopher:// schemes passed into Sitefinity SDK routes.
- Spikes in server-initiated DNS lookups for domains not associated with normal application behavior.
Detection Strategies
- Inspect reverse proxy and web application firewall logs for user-supplied URL parameters forwarded to Sitefinity SDK endpoints.
- Correlate inbound HTTP requests to the Next.js application with outbound connections from the same process to identify server-proxied traffic patterns.
- Review egress firewall logs for connections originating from the application tier to cloud metadata services or management interfaces.
Monitoring Recommendations
- Enable egress filtering and alert on any outbound traffic from the Sitefinity Next.js host to internal management ranges or metadata IPs.
- Instrument the Node.js runtime with request tracing to log every outbound fetch or http call with its destination.
- Baseline normal outbound destinations for the application and alert on deviations.
How to Mitigate CVE-2026-92931
Immediate Actions Required
- Inventory all applications using @progress/sitefinity-nextjs-sdk and identify versions between 15.1.8326 and 15.4.8637.
- Upgrade the SDK to the fixed version listed in the Progress security advisory.
- Restrict outbound network access from the Next.js application tier to only required destinations until patching is complete.
Patch Information
Progress has published remediation guidance in the Progress Sitefinity Security Advisory. Upgrade the @progress/sitefinity-nextjs-sdk dependency to the version identified by the vendor and redeploy the application.
Workarounds
- Deploy an egress proxy that enforces an allowlist of permitted outbound destinations for the Next.js application.
- Block requests to link-local and private IP ranges (for example 169.254.0.0/16, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) from the application host.
- Disable or guard any SDK routes that accept user-supplied URLs until the patched version is deployed.
# Configuration example
npm ls @progress/sitefinity-nextjs-sdk
npm install @progress/sitefinity-nextjs-sdk@latest
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

