langgenius dify-web up to 1.6.0 missing standardized error handling mechanism

Summaryinfo

A vulnerability identified as problematic has been detected in langgenius dify-web up to 1.6.0. Affected is an unknown function. This manipulation causes missing standardized error handling mechanism. This vulnerability is tracked as CVE-2025-11750. The attack is only possible within the local network. No exploit exists.

Detailsinfo

A vulnerability was found in langgenius dify-web up to 1.6.0. It has been declared as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a missing standardized error handling mechanism vulnerability. The CWE definition for the vulnerability is CWE-544. The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses. As an impact it is known to affect integrity. The summary by CVE is:

In langgenius/dify-web version 1.6.0, the authentication mechanism reveals the existence of user accounts by returning different error messages for non-existent and existing accounts. Specifically, when a login or registration attempt is made with a non-existent username or email, the system responds with a message such as "account not found." Conversely, when the username or email exists but the password is incorrect, a different error message is returned. This discrepancy allows an attacker to enumerate valid user accounts by analyzing the error responses, potentially facilitating targeted social engineering, brute force, or credential stuffing attacks.

The advisory is shared at huntr.com. This vulnerability is known as CVE-2025-11750 since 10/14/2025. The exploitation appears to be easy. The attack can only be initiated within the local network. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/31/2025).

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

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

Productinfo

Vendor

• langgenius

Name

• dify-web

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6.0

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