MaxKB's webhook trigger endpoint allowed unauthenticated requests before version 2.9.0. The authentication logic returned a default success value, letting anyone who knew a trigger ID invoke webhook tasks. This enabled attackers to trigger arbitrary bound tasks, exposing the system to potential data exfiltration or code execution depending on the configured task. The weakness is an authentication bypass (CWE-287) with missing access control (CWE-306).

The vulnerability affects MaxKB, an open‑source AI assistant for enterprise systems. Any deployment using MaxKB prior to or including the 2.8.x releases is impacted, as the authentication bypass exists for all webhook trigger endpoints (/api/trigger/v1/webhook/{trigger_id}). No specific patch version is available except the 2.9.0 release, which contains the fix.

The CVSS score is 7.5, indicating a high severity. EPSS is not available, so current exploitation likelihood is unknown, and the vulnerability is not listed in the CISA KEV catalog. Attackers can perform the exploit remotely by sending a request to the webhook trigger endpoint with a valid trigger ID, bypassing authentication entirely and executing the associated task. This represents a serious authentication flaw that can lead to privilege escalation or system compromise if task logic is malicious.