CVE-2025-63388

The vulnerable endpoint implements a CORS policy that dynamically reflects the value of the Origin header sent by the client, instead of restricting it to trusted domains. At the same time, the response contains the Access-Control-Allow-Credentials: true header, which allows the browser to include session cookies or other authentication data in the request. In practice, this means that a malicious website can trick a logged-in user into visiting it, and then execute authenticated requests on their behalf to the Dify instance. The vendor questions the severity of the vulnerability, arguing that requests with authentication credentials do not provide access to resources inaccessible to unauthenticated users.

An attacker who tricks a logged-in user into visiting a malicious website can execute authenticated requests on their behalf to the Dify panel, potentially gaining access to sensitive configuration data or system functions. The scope of an effective attack is disputed and depends on the actual access control mechanisms on the remaining endpoints.

Apply patches available from the vendor according to references. As a workaround, it is recommended to configure a CORS policy with an explicit whitelist of trusted domains instead of dynamically reflecting the Origin header, and also consider removing the Access-Control-Allow-Credentials: true header for public endpoints or limiting it only to trusted sources.

Langgenius Dify v1.9.1 — /console/api/system-features endpoint