CVE-2026-92931
validatedZero produced an exploit or a check.GHSA-j5cj-5p4r-rxhj ↗EUVD-2026-92430 ↗
description
@progress/sitefinity-nextjs-sdk versions 15.1.8326 through 15.4.8637 are affected by a server-side request forgery flaw. A remote attacker may cause a server using an affected version to send requests to attacker-controlled hosts, potentially exposing sensitive information.
mitigation
Upgrade @progress/sitefinity-nextjs-sdk to version 15.4.8638 or later. Prioritize updates for deployments that process remote attacker-controlled input.
fixed in 15.4.8638
outcome
Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-05 13:06Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-92931
{ "etk_id": "ETK-2026-652", "cve_id": "CVE-2026-92931", "display_id": "CVE-2026-92931", "ghsa_id": "GHSA-j5cj-5p4r-rxhj", "euvd_id": "EUVD-2026-92430", "status": "published", "anchor_state": "anchored", "title": "Server-side request forgery in @progress/sitefinity-nextjs-sdk", "summary": "@progress/sitefinity-nextjs-sdk versions 15.1.8326 through 15.4.8637 are affected by a server-side request forgery flaw. A remote attacker may cause a server using an affected version to send requests to attacker-controlled hosts, potentially exposing sensitive information.", "mitigation": "Upgrade @progress/sitefinity-nextjs-sdk to version 15.4.8638 or later. Prioritize updates for deployments that process remote attacker-controlled input.", "vendor": "Progress Software", "product": "@progress/sitefinity-nextjs-sdk", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 15.1.8326, < 15.4.8638" ], "ecosystem": null, "fixed_versions": [ "15.4.8638" ], "package_name": "@progress/sitefinity-nextjs-sdk", "purl": null } ], "cwes": [ 918 ], "cvss_score": 10, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H", "epss_score": 0.0026, "epss_percentile": 0.1703, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "mechanism_verified", "exploit": false, "pipeline_minutes": 23.098711283333333, "t0_at": "2026-10-05T13:06:02.081000+00:00", "signals": { "check": { "at": "2026-10-05T16:23:38.257010+00:00", "days": 0.137224259375, "is_lower_bound": false, "measured_at": "2026-10-05T13:06:02.081000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-05T13:06:02.081000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-05T13:06:02.081000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-92931" } } }
published 2026-10-05 13:30Z
last change 2026-10-21 17:00Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.