ItzCrazyKns Vane Missing Authentication Vulnerability in API Component

Vulnerability

A vulnerability exists in ItzCrazyKns Vane versions through 1.12.1, where the API component's route.ts file lacks proper authentication. This oversight allows remote attackers to access sensitive functionalities without authorization. The vulnerability's complexity is high, making exploitation challenging, although it has been publicly disclosed and could be utilized once basic authentication is implemented.

Impact

Exploitation of this vulnerability could lead to unauthorized access to all API endpoints, allowing attackers to read and modify the application's configuration, including sensitive API keys. Additionally, it could enable them to access and delete chat histories, upload arbitrary files, manage LLM model providers, consume LLM API quotas, hijack active sessions, and redirect search infrastructure to attacker-controlled servers.

Reproduction

The vulnerability can be reproduced by sending an unauthenticated GET request to the '/api/config' endpoint. This request will return the full configuration, including all API keys for LLM providers, in plaintext. The absence of authentication middleware allows this exploitation to occur without any authorization checks.

Remediation

To address this vulnerability, it is recommended to add authentication middleware to the API routes, implement role-based access control, and separate public and private configuration data. Additionally, encrypting sensitive information at rest and conducting an audit of the application's API endpoints for similar vulnerabilities would be beneficial.

Added: May 26, 2026, 8:45 PM
Updated: May 26, 2026, 8:45 PM

Vulnerability Rating

Custom Algorithm
spread
0.0
impact
2.5
exploitability
8.7
remediation
0.0
relevance
9.3
threat
6.4
urgency
2.9
incentive
4.2

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.