dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-44651

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SillyTavern is a locally installed user interface that allows users to interact with text generation large language models, image generation engines, and text-to-speech voice models. Prior to 1.18.0, 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. This vulnerability is fixed in 1.18.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SillyTavern versions prior to 1.18.0 contain a reflected cross-site scripting (XSS) vulnerability. When the fetch(url) call fails, the application returns a 500 error that includes the attacker-controlled URL parameter (req.params.url) without HTML escaping, allowing injection of malicious scripts into the error response.

MitigationUpgrade to SillyTavern 1.18.0 or later, which implements proper HTML escaping of the URL parameter before including it in error messages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SillyTavern is running
    Identify the SillyTavern process or check for the service listening on its typical port (usually 8000 or 8080). Access the web interface in a browser or verify via network scan.
  2. Determine installed version
    Check the version number of SillyTavern. This is typically visible in the web UI footer, in package.json if self-hosted, or via the startup logs. Compare your version to the affected range: any version prior to 1.18.0 is vulnerable.
  3. Identify if URL-fetching feature is enabled
    SillyTavern includes features that fetch content from external URLs (such as connecting to LLM backends, loading extensions, or retrieving remote content). Verify if any feature requiring URL input is configured or accessible.
  4. Check for error response reflection
    Trigger a fetch failure by providing an invalid or unreachable URL to any SillyTavern endpoint that accepts a URL parameter. Inspect the 500 error response to see if the URL value appears verbatim (unescaped) in the error message.

A user is affected if they run SillyTavern versions prior to 1.18.0 AND have access to features that accept URL parameters, AND error responses display the unsanitized URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SillyTavern 1.18.0 or later, which implements proper HTML escaping of the URL parameter before including it in error messages.

Recommended fix High confidence

1.18.0

  1. 1. Check current SillyTavern version by navigating to the SillyTavern interface and looking at the version number displayed, or check via command line if installed programmatically
  2. 2. Upgrade SillyTavern to version 1.18.0 or later by pulling the latest release from the official GitHub repository (github.com/SillyTavern/SillyTavern)
  3. 3. Restart the SillyTavern service to apply the update
  4. 4. Verify the upgrade was successful by confirming the version displayed in the UI shows 1.18.0 or higher
  5. 5. Test that the proxy error endpoint no longer reflects unescaped URL parameters by triggering a proxy error and inspecting the response

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44651 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data