The vulnerability stems from a missing authorization check in MaxKB’s management chat‑record routes. A user can provide any application_id in the path while the system loads records based on a global chat_id, which allows reading and potentially modifying chat history that belongs to another application within the same workspace. This leads to a confidentiality breach of sensitive conversation data and also permits an attacker to copy proprietary answers into their own knowledge base, creating integrity risks.

1Panel-dev MaxKB versions 2.10.2‑lts and earlier are affected. No patch is yet released, so systems running these versions remain vulnerable. The issue originates in the management chat‑record routes that do not enforce ownership of the chat record on the application path.

CVSS score 4.2 indicates moderate risk, EPSS not available, and the vulnerability is not listed in the CISA KEV catalog. An attacker only needs to know a valid global chat_id and supply an arbitrary application_id path, both of which can be discovered through normal application usage or minimal reconnaissance. The lack of an authorization check means exploitation can be performed from any authenticated user within the same workspace, making the attack straightforward for a normal user with knowledge of chat ids.