CVE-2026-44651: SillyTavern has a reflected XSS vulnerability in the CORS proxy middleware
Resolution Fixed in SillyTavern 1.18.0: a user-provided URL is no longer reflected in the HTTP response body. Overview - Vulnerability Type: XSS - Affected Location: src/middleware/corsProxy.js:40 - Trigger Scenario: reflected XSS in CORS proxy error response Root Cause When fetch(url) throws, the code sends: res.status(500).send('Error occurred while trying to proxy to: ' + url + ' ' + error).
Published May 12, 2026 · Updated Jun 9, 2026
Affected packages
sillytavern
- Ecosystem
- npm
- Affected
- <= 1.17.0
- Fixed in
- 1.18.0
- Check
npm ls sillytavern
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Resolution
Fixed in SillyTavern 1.18.0: a user-provided URL is no longer reflected in the HTTP response body.
Overview
- Vulnerability Type: XSS
- Affected Location:
src/middleware/corsProxy.js:40 - Trigger Scenario: reflected XSS in CORS proxy error response
Root Cause
When fetch(url) throws, the code sends: res.status(500).send('Error occurred while trying to proxy to: ' + url + ' ' + error). The url value is attacker-controlled (req.params.url) and is not HTML-escaped before rendering.
Source-to-Sink Chain
- Source (user-controlled input)
- Entry point:
GET /proxy/:url(*)
- Data flow
- Code analysis shows concrete propagation into this sink:
- vulnerability title:
Reflected XSS in CORS proxy error response - sink location reached by attacker-controlled input:
src/middleware/corsProxy.js:40 - The same sink behavior is confirmed by controlled execution observations.
- Sink (dangerous operation)
- Sink location:
src/middleware/corsProxy.js:40 - Vulnerable behavior: reflected XSS in CORS proxy error response
Exploitation Preconditions
- The attacker can inject controllable content into a rendered response.
- The vulnerable rendering context does not apply strict output encoding/sanitization.
- A victim user opens the affected page or response.
Risk
This issue enables script execution in the victim context and can compromise session or data integrity.
Impact
An attacker may run arbitrary JavaScript in the victim context, steal tokens, and manipulate user-visible behavior.
Remediation
- Never concatenate raw user input into HTML error responses.
- If URL echo is required, HTML-escape it or force plain-text output.
- Re-enable/strengthen CSP to reduce reflected injection impact.
Credited to FORIMOC.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-46372
SillyTavern: SSRF in SearXNG Search Proxy via Unvalidated baseUrl
high8.5May 19, 2026CVE-2026-44648
SillyTavern: Existing sessions are not invalidated after password change, allowing session reuse and account takeover
high7.5May 12, 2026CVE-2026-44649
SillyTavern has Authentication Bypass via SSO Header Injection
critical9.8May 12, 2026CVE-2026-44650
SillyTavern has a Path Traversal issue
critical9.1May 12, 2026CVE-2026-44652
SillyTavern has a SSRF vulnerability in the CORS proxy middleware
medium6.9May 12, 2026CVE-2026-34522
SillyTavern has a path traversal in `/api/chats/import` allows arbitrary file write outside intended chat directory
high8.1Apr 1, 2026
