A critical authentication bypass and insecure default configuration in AnythingLLM allows unauthenticated attackers to interact with the application via local network requests.

The application fails to enforce authentication on HTTP endpoints and WebSocket connections by default, and implements a permissive CORS policy that accepts requests from any origin. This allows an unauthenticated attacker, positioned on the local network, to perform unauthorized actions.

The vulnerability presents a significant risk to data integrity and confidentiality, as unauthorized parties can interact with the LLM context or administrative functions. Given the CVSS score of 7.1, this is a High severity issue that could lead to the exposure of sensitive documents or the manipulation of chat context, potentially resulting in unauthorized information disclosure or system misuse.

Immediate Action: Upgrade to the latest version of AnythingLLM as specified by the vendor, and ensure that strong authentication, specifically a password or API key, is configured immediately upon deployment.

Proactive Monitoring: Review application and server access logs for anomalous requests originating from local network IP addresses, particularly those targeting API endpoints or WebSocket connections.

Compensating Controls: Restrict network access to the AnythingLLM instance using host-based firewalls to ensure that only trusted internal devices can communicate with the application, as browser-level protections like Private Network Access may not be sufficient in all network environments.

Public Exploit Available: Unknown.

This vulnerability highlights the danger of relying on default configurations that lack authentication. Administrators must prioritize updating to the latest version and enforcing mandatory access controls, such as API keys or user passwords, to prevent unauthorized interaction with the application. Failure to address this configuration flaw leaves the application exposed to any actor with local network access.