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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-63387US | — | — | ||
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 authenti… | ||||
references
External citations — patches, advisories, analysis.
- https://gist.github.com/Cristliu/cddc0cbbf354de51106ab63a11be94afADVISORY
- https://gist.github.com/Cristliu/dfc5f3a31dc6d7fff2754867e5c649a5WEB
- https://github.com/langgenius/dify/discussionsREPORT
- https://github.com/langgenius/dify/issues/31368#issuecomment-3783712203REPORT
- https://github.com/langgenius/dify/pull/31392FIX
- https://github.com/langgenius/dify/pull/31417FIX
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan