Dify 1.9.1 Endpoint system-features improper authentication

Summaryinfo

A vulnerability has been found in Dify 1.9.1 and classified as critical. This impacts an unknown function of the file /console/api/system-features of the component Endpoint. The manipulation leads to improper authentication. This vulnerability is referenced as CVE-2025-63387. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Dify 1.9.1. It has been rated as critical. This issue affects an unknown part of the file /console/api/system-features of the component Endpoint. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-63387 since 10/27/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/23/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-204368). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Dify

Version

• 1.9.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion