GHSA-ccfq-2454-f5xw
GHSA-ccfq-2454-f5xw is a Server-Side Request Forgery (SSRF) vulnerability in sillytavern. O3 Security confirms whether GHSA-ccfq-2454-f5xw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
SillyTavern has a SSRF vulnerability in the CORS proxy middleware
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-ccfq-2454-f5xw.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
sillytavernnpmDescription
Resolution
SillyTavern 1.18.0 added a generic server-side request filter (Private Request Whitelisting). Since we expect users to use the application in a trusted environment, the filter is disabled by default, however it is strongly advised to be enabled and properly configured when an instance is being hosted over a network, as suggested by a console warning message and an officially published security checklist for administrators.
Documentation:
- https://docs.sillytavern.app/administration/config-yaml/#private-address-whitelisting
- https://docs.sillytavern.app/administration/#security-checklist
Note on future SSRF findings
Since the request filter applies to the entire application, no SSRF vulnerabilities against individual endpoints will be accepted, unless it has been proven that a properly configured and enabled filter can be bypassed in an undocumented way. Only advisories disclosed before the 1.18.0 release will be posted if their concern is SSRF.
Overview
- Vulnerability Type: SSRF
- Affected Location:
src/middleware/corsProxy.js:31 - Trigger Scenario: SSRF in optional CORS proxy
Root Cause
corsProxyMiddleware forwards req.params.url directly into fetch(url, ...). It only blocks circular requests to its own host and does not enforce destination allowlist or private/loopback restrictions, enabling SSRF.
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:
SSRF in optional CORS proxy - sink location reached by attacker-controlled input:
src/middleware/corsProxy.js:31
- vulnerability title:
- The same sink behavior is confirmed by controlled execution observations.
- Sink (dangerous operation)
- Sink location:
src/middleware/corsProxy.js:31 - Vulnerable behavior: SSRF in optional CORS proxy
Exploitation Preconditions
- The attacker can control or influence a URL/endpoint parameter.
- The server can access internal or sensitive network targets.
- Outbound request validation or redirect controls are insufficient.
Risk
This issue can be used to pivot network access and reach unintended internal resources.
Impact
An attacker may access internal network services or metadata endpoints and exfiltrate sensitive responses.
Remediation
- Enforce strict destination allowlist for proxy targets.
- Block loopback, link-local, RFC1918, and metadata address ranges.
- Apply the same destination validation to redirects.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | sillytavern | all versions | 1.18.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sillytavern. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sillytavern to 1.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ccfq-2454-f5xw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-ccfq-2454-f5xw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-ccfq-2454-f5xw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-ccfq-2454-f5xw in your dependencies?
O3 detects GHSA-ccfq-2454-f5xw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.