# CVE-2026-92931: CWE-918: Server-Side Request Forgery in the Progress Sitefinity Next.js Renderer SDK

> A remote attacker can exploit Server-Side Request Forgery in the Sitefinity Next.js SDK to access sensitive information via server-side requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-j5cj-5p4r-rxhj

## What is CVE-2026-92931?

CVE-2026-92931 is a high-severity server-side request forgery vulnerability in @progress/sitefinity-nextjs-sdk, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CWE-918: Server-Side Request Forgery in the Progress @progress/sitefinity-nextjs-sdk npm package versions 15.1.8326 through 15.4.8637 may allow a remote attacker to make server-side requests to an attacker-controlled host, potentially exposing sensitive information.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-92931?


## How do I fix CVE-2026-92931?

No fix has been published for CVE-2026-92931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92931 being exploited?

There is no known exploitation of CVE-2026-92931 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92931 and fix it if it is affected.

What it is: CVE-2026-92931 is a high-severity server-side request forgery vulnerability in @progress/sitefinity-nextjs-sdk, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92931 in the wild and no public exploit code.

Affected product: @progress/sitefinity-nextjs-sdk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92931/ (Markdown: https://insights.sbomify.com/CVE-2026-92931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92931
- OSV: https://osv.dev/vulnerability/CVE-2026-92931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92931/
Summaries are generated and may contain mistakes; the official description above is the record.