Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous ac

Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous access to sensitive system configuration data. NOTE: The maintainer states that the endpoint is unauthenticated by design and serves as a bootstrap mechanism required for the dashboard initialization. They also state that the description inaccurately classifies the returned data as sensitive system configuration, stating that the data is non-sensitive and required for client-side rendering. No PII, credentials, or secrets are exposed.

CVSS 3.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Severity from

the CVSS score

Also known as

CVE-2025-63387

• gist.github.com/Cristliu/dfc5f3a31dc6d7fff2754867e5c649a5
• gist.github.com/Cristliu/cddc0cbbf354de51106ab63a11be94af
• github.com/langgenius/dify/discussions
• github.com/langgenius/dify/issues/31368#issuecomment-3783712203
• github.com/langgenius/dify/pull/31392
• github.com/langgenius/dify/pull/31417