WebHigh 8.8
CVE-2026-92931
SSRF in Progress Sitefinity Next.js SDK allows server-side requests to attacker hosts
How scary is it?
updated 22 Nov 2026- Yes
Works without logging in1
No account needed, but a person has to act, such as opening a link or a file (CVSS PR:N, UI:R).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Progress Software @progress/sitefinity-nextjs-sdk in an affected version>= 15.1.8326 and < 15.4.8638
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
A person takes an action, such as opening a link or a file
CVSS user interaction: required (UI:R). A victim must click, open or otherwise cooperate.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Recommendation, AI-writtenUpgrade to vendor fixed release when published; block/restrict outbound HTTP, validate URLs, apply WAF rules.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
- CVSS
- 8.8Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.26%chance of exploitation in the next 30 daystop 82% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 5 Oct 2026analysed here 6 Oct 2026
Summary
Impact
SSRF lets attackers force server HTTP requests to attacker-controlled or internal hosts, risking data exposure, access to internal services, and lateral pivoting.
Triage
Executive summary (AI-written)
CVE-2026-92931 is a critical security vulnerability identified in the Progress Sitefinity Next.js SDK, with a CVSS score of 8.8, indicating a significant risk. This Server-Side Request Forgery (SSRF) flaw allows attackers to manipulate server-side requests, potentially leading to unauthorized access to sensitive data and internal services. While the vulnerability is crucial for organizations using affected versions of the SDK (ranging from 15.1.8326 to 15.4.8637), it's not a widespread issue that would disrupt core operations across most enterprises. However, the business impact could be significant for those directly affected, necessitating prompt attention to mitigate risks associated with data exposure and lateral movement within networks. As of now, there is no patch available from the vendor, but organizations are advised to take immediate action by preparing to implement the forthcoming patch upon its release. In the interim, companies should prioritize securing their environments by blocking or restricting outbound HTTP requests, validating URL inputs, and applying Web Application Firewall (WAF) rules to reduce exposure. By proactively addressing this vulnerability, businesses can safeguard their critical assets and maintain operational integrity.
Technical analysis (AI-written)
CVE-2026-92931 is a Server-Side Request Forgery (SSRF) vulnerability affecting the @progress/sitefinity-nextjs-sdk npm package, with affected versions spanning from 15.1.8326 to 15.4.8637. SSRF vulnerabilities allow attackers to induce the server to send unauthorized requests to internal or external services, potentially exposing sensitive information or leveraging internal network services for further exploits. With a CVSS score of 8.8, the vulnerability poses a substantial risk, particularly for web applications that utilize the affected SDK in their architecture. An attacker exploiting this vulnerability can manipulate requests to interact with internal systems, potentially leading to data exfiltration or the discovery of additional vulnerabilities within the internal network. This makes SSRF vulnerabilities particularly dangerous as they can provide an entry point for lateral movement, allowing attackers to pivot to more secure systems that typically wouldn’t be accessible externally. The exploitation complexity is considered moderate; an attacker would primarily need to authenticate to the application and then construct malicious URLs to exploit the underlying flaw. While an attacker wouldn't require advanced skills, effective exploitation could still necessitate some understanding of the application's functionality and the internal infrastructure it accesses. Mitigation strategies are essential for organizations currently using the SDK. Aside from promptly applying the vendor's patch once it becomes available, organizations should take proactive measures to block or restrict outbound HTTP/S traffic to untrusted destinations. Furthermore, implementing strict URL validation protocols and configuring a Web Application Firewall (WAF) with rules that can help detect and block malicious requests will bolster the security posture against this type of vulnerability. Given the potential impact of this SSRF exposure, security teams should prioritize this vulnerability in their remediation plans and conduct thorough testing of their applications to identify and mitigate any exploitation points. Regular updates to dependency management and a review of web service interactions should be standard practices to avoid similar vulnerabilities in the future.
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Progress Software @progress/sitefinity-nextjs-sdk | >= 15.1.8326 and < 15.4.8638Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- @progress/sitefinity-nextjs-sdk npm versions 15.1.8326 - 15.4.8637
Fix and mitigation
Action required
Patch when possible
WAF and other mitigations
Can a WAF block it? No. The vulnerability involves server-side request forgery (SSRF) where the server makes requests to attacker-controlled hosts based on input. Such requests typically look like normal URLs and cannot be reliably distinguished by a web application firewall without blocking legitimate requests.
Also consider: egress filter · IMDSv2
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 6 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 5 Oct 2026Published
- 6 Oct 2026CISA SSVC assessment: exploitation none1 day later
- 6 Oct 2026Analysed by vulneraibility.comsame day later
- 6 Oct 2026CVE record last updatedsame day later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2026-92931 being exploited?
Not confirmed. CVE-2026-92931 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-92931?
CVE-2026-92931 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92931?
Not known from our data. No patch reference has been recorded for CVE-2026-92931, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-92931 affect?
CVE-2026-92931 affects @progress/sitefinity-nextjs-sdk npm versions 15.1.8326 - 15.4.8637. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92931?
Upgrade to vendor fixed release when published; block/restrict outbound HTTP, validate URLs, apply WAF rules.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- community.progress.com /s/article/Sitefinity-Critical-Security-Advisory-for-Addressing-Security-Vulnera
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.