Compliance Impact

The vulnerability is a reflected Cross-Site Scripting (XSS) issue that allows attackers to inject malicious JavaScript code into error responses, which can execute in the context of a victim user's session.

Such XSS vulnerabilities can lead to unauthorized access to user tokens or manipulation of user-visible behavior, potentially compromising user data confidentiality and integrity.

While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, the presence of an XSS vulnerability that could lead to data exposure or unauthorized access may negatively impact compliance with these regulations, which require protection of personal and sensitive data.

Mitigations such as proper HTML escaping, avoiding direct user input concatenation in responses, and enforcing Content Security Policy (CSP) are recommended to reduce the risk and help maintain compliance.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-44651 is a reflected Cross-Site Scripting (XSS) vulnerability in SillyTavern versions 1.17.0 and earlier. It occurs in the CORS proxy middleware where an attacker-controlled URL is included in error messages without proper HTML escaping. When a fetch operation fails, the application sends a 500 error response containing the raw URL, which can include malicious JavaScript code. This code is then executed in the victim user's browser context.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows attackers to inject and execute malicious JavaScript code in the context of a victim user's session. This can lead to theft of sensitive information such as authentication tokens, manipulation of user-visible content, or other malicious actions performed on behalf of the user without their consent.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by checking if the SillyTavern application version is 1.17.0 or earlier, as these versions contain the reflected XSS issue in the CORS proxy middleware.

To detect exploitation attempts on your system or network, you can monitor HTTP 500 error responses from the SillyTavern server that include user-controlled URL parameters reflected in the response body without HTML escaping.

A practical approach is to capture and inspect HTTP traffic to the SillyTavern server for error responses containing suspicious or unexpected URL parameters.

Example commands to help detect this vulnerability or exploitation attempts include:

• Using curl to send a request with a crafted URL parameter and observe if the response reflects it unescaped in an error message: curl -i 'http://<sillytavern-host>/proxy/<test_payload>'
• Using grep or similar tools on server logs to find HTTP 500 responses containing user-controlled URL parameters: grep '500' /path/to/sillytavern/logs | grep '<suspicious_url>'
• Using a web proxy or interception tool (e.g., Burp Suite) to analyze responses for reflected user input in error messages.

Useful 0 Not Useful 0

Mitigation Strategies

The primary mitigation step is to upgrade SillyTavern to version 1.18.0 or later, where this vulnerability has been fixed by preventing the raw URL from being reflected in error responses.

If upgrading immediately is not possible, apply the following interim mitigations:

• Avoid direct concatenation of user input into HTML responses.
• Apply proper HTML escaping or output user input as plain text in error messages.
• Strengthen Content Security Policy (CSP) headers to reduce the impact of reflected XSS attacks.

Useful 0 Not Useful 0