Horizon Alert
Summary of the vulnerability and why it matters
This advisory describes a critical vulnerability in SillyTavern, a user interface for AI models. An unauthenticated attacker could potentially delete user-installed extensions on the affected system. The main concern is confirming relevance and exposure, as the tool is designed for local use.
- Sensitive files can be deleted by attackers.
- Unauthenticated access to delete extensions.
- Confirm if this locally installed tool is in use.
Attack Path
How an attacker could exploit the issue
An attacker can initiate an attack by sending a specially crafted request to the SillyTavern application over the network. Because no authentication is needed, the attacker can target the `/api/extensions/delete` endpoint and provide a specific input that circumvents security checks. This allows the attacker to delete all user extensions.
- No authentication required.
- Malicious input to delete extensions.
- Deletes all user extensions.
Live Threat
Current exploitation, exposure, and threat context
The vulnerability in SillyTavern's `/api/extensions/delete` endpoint could allow an unauthenticated attacker to recursively delete the entire user extensions directory. This could occur when an attacker sends a crafted POST request to the endpoint with a specific value that bypasses filename sanitization. This action would impact the integrity and availability of the SillyTavern installation by removing all installed extensions.
- User extensions directory is at risk.
- Exposure via unauthenticated API endpoint.
- Loss of installed extensions.
Operational Fix
Recommended remediation, mitigation, and detection steps
This vulnerability affects SillyTavern, a locally installed user interface. Given its typical deployment as a personal tool, ownership likely resides with individual users or desktop support teams responsible for user-provided applications. The first critical step is to identify any instances of SillyTavern on the network, confirm its accessibility and business criticality, and then coordinate remediation with the accountable owner.
- User or desktop support teams own the issue.
- Verify affected user installations and accessibility.
- Plan remediation with accountable users.