CVE-2025-63387: High severity npm/dify vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-63387?
CVE-2025-63387 is classified as a high severity vulnerability due to its ability to allow unauthenticated access to sensitive API endpoints.
How do I fix CVE-2025-63387?
To fix CVE-2025-63387, implement proper authorization checks on the /console/api/system-features endpoint and restrict access to authenticated users.
What kind of attacks can exploit CVE-2025-63387?
CVE-2025-63387 can be exploited by attackers to gain unauthorized information or control over system features without needing authentication.
Which versions of Dify are affected by CVE-2025-63387?
Dify version 1.9.1 is affected by CVE-2025-63387, specifically related to insecure permissions for API access.
Is there a patch available for CVE-2025-63387?
As of now, a specific patch for CVE-2025-63387 has not been released, and users should monitor updates from the Dify maintainers for a resolution.