VulnerabilityPublished 22 Oct 2025

CVE-2025-11750: langgenius/dify · Missing Standardized Error Handling Mechanism

Affects langgenius/difySource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: evidence found.
nuclei template: Dify - User Enumeration via "Account not found" Message
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-11750, organizations should implement standardized and generic error messages for authentication failures, ensuring that responses do not reveal whether a username or email exists. For example, use a uniform message such as "Invalid username or password" for all failed login attempts. Additionally, rate limiting and account lockout mechanisms should be enforced to reduce the risk of brute force and enumeration attacks. Multi-factor authentication (MFA) should be deployed to add an extra layer of security beyond passwords. Monitoring and alerting on suspicious login patterns can help detect enumeration attempts early. Developers should review authentication code to ensure compliance with CWE-544 guidelines and apply patches or updates from the vendor once available. Conducting regular security assessments and penetration tests focusing on authentication flows is also recommended. Finally, educating users about phishing and credential reuse risks can reduce the effectiveness of attacks facilitated by enumeration.

Description

CVE-2025-11750 is a medium severity vulnerability in langgenius/dify-web version 1.6.0 where the authentication mechanism leaks user account existence information through distinct error messages. This allows attackers to enumerate valid usernames or emails by analyzing login or registration error responses. Although it does not directly compromise passwords or system integrity, it facilitates targeted attacks such as social engineering, brute force, or credential stuffing. The vulnerability arises from missing standardized error handling (CWE-544), causing inconsistent error messages for non-existent versus existing accounts with incorrect passwords. No known exploits are currently reported in the wild. The CVSS score is 4.3, reflecting limited impact on confidentiality and integrity without affecting availability. European organizations using langgenius/dify-web should prioritize uniform error messaging and implement additional protections against account enumeration to reduce attack surface.

Impact

For European organizations, this vulnerability primarily increases the risk of targeted attacks by enabling attackers to enumerate valid user accounts. This can lead to more effective phishing campaigns, social engineering, brute force attempts, and credential stuffing attacks, potentially resulting in unauthorized access if weak or reused passwords are present. While the vulnerability itself does not allow direct compromise of accounts or systems, it facilitates reconnaissance that can be leveraged in multi-stage attacks. Organizations in sectors with high-value user data or critical services—such as finance, healthcare, and government—may face increased risk from attackers exploiting this information leakage. Additionally, GDPR and other European data protection regulations emphasize minimizing personal data exposure, and user enumeration could be considered a data privacy concern. The vulnerability may also erode user trust if exploited, impacting reputation and compliance posture.

CWE-544Missing Standardized Error Handling Mechanism (opens in a new tab)
Base weakness
The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.
Architecture and Design
define a strategy for handling errors of different severities, such as fatal errors versus basic log events. Use or create built-in language features, or an external package, that provides an easy-to-use API and define coding standards for the detection and handling of errors.
OWASP ASVS 4.0.3
V7.4.2 (opens in a new tab)
V9.2.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

huntr.com/bounties/e7359f9f-c004-4304-9de9-753622d370a1 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 29 Oct 2025, 13:57 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-544

Technical details

References

Community reviews

Related threats