Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach LDAP-backed Frappe endpoint
-
ExploitSupply crafted LDAP filter syntax in parameter
-
ExecutionInjection alters directory query logic
-
ImpactEnumerate or disclose directory data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization LDAP query parameterization
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires that the Frappe instance has LDAP integration enabled/configured for directory or authentication lookups - this is the attack requirement reflected by CVSS AT:P, and instances not using LDAP are not exploitable. The attacker must be able to reach one of the specific endpoints that pass user-supplied parameters into LDAP queries without sanitization; no authentication is required per PR:N and no user interaction per UI:N. Limiting factors: exploitation is confined to directory-query manipulation (confidentiality-oriented, VI:N/VA:N) and only affects deployments with the LDAP feature active, substantially narrowing the real-world exposed population below the raw network-reachable figure. |
| Impact | This is a medium-severity LDAP injection (CWE-90) rated CVSS 4.0 6.3 with vector AV:N/AC:L/AT:P/PR:N/UI:N and a confidentiality-only impact (VC:L, VI:N, VA:N, no scope change). The network vector and PR:N indicate a remote, unauthenticated reachable flaw, but the AT:P (Attack Requirements: Present) metric is the critical qualifier: exploitation depends on Frappe actually being configured to use LDAP for directory/authentication queries - it is not a universally exploitable condition. There is no EPSS score provided, the CVE is NOT on the CISA KEV list, and no public proof-of-concept is referenced, so there is no public exploit identified at time of analysis. Weighing the signals: the CVSS confidentiality-limited impact, the deployment-dependent attack requirement, and the absence of KEV/POC/EPSS data together point to a genuine but moderate, non-urgent issue rather than a top-tier emergency - it warrants patching on a normal remediation cycle for Frappe/ERPNext instances that use LDAP, and is lower priority for instances that do not. No conflicting signals are present, but note the input lacks EPSS entirely, so exploitation-probability cannot be quantified. |
| Exploit ScenarioDerived | A remote attacker sends requests to a Frappe endpoint that passes user-supplied parameters unsanitized into an LDAP query, injecting crafted LDAP filter syntax (e.g., wildcards or boolean operators) to alter the directory lookup. By manipulating the filter the attacker can broaden or redirect the query to enumerate directory entries or influence authentication-related lookups. No public exploit code is referenced, and exploitation requires the target to have LDAP integration configured (reflected by the CVSS AT:P metric). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
LDAP injection (CWE-90) in Frappe Framework allows unauthenticated remote attackers to manipulate directory queries by injecting crafted LDAP filter syntax through unsanitized endpoint parameters, with an impact limited to information disclosure (VC:L, VI:N, VA:N). The flaw affects Frappe releases before 14.99.2 and 15.x releases before 15.86.0, and is rated 6.3 under CVSS 4.0 (AV:N/AC:L/AT:P/PR:N/UI:N); exploitability is conditional because the instance must have LDAP integration actively configured, which is the attack requirement reflected by AT:P. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
RemediationAI
Upgrade to the vendor-released fix versions: Frappe 14.99.2 for the 14.x line and Frappe 15.86.0 (or later) for the 15.x line, as documented in advisory GHSA-qrq5-v93p-8xhw. If immediate upgrade is not possible, the most effective compensating control is to disable LDAP integration entirely (set the LDAP configuration off and revert affected users to local authentication) until the patch is applied - the trade-off is loss of centralized directory authentication and the administrative effort of managing local credentials. Where LDAP must remain active, reduce exposure by restricting network access to the affected endpoints to trusted networks or administrative ranges via reverse-proxy ACLs or IP allowlisting, accepting that this limits legitimate user access to those paths; additionally, run the LDAP bind account with the least privilege necessary and scope its search base and permissions so injected filters cannot reach sensitive directory attributes. Monitoring LDAP server logs for malformed or wildcard-heavy filter queries from the Frappe host can provide early detection, but is a detective rather than preventive control. Consult the VulnCheck advisory at https://www.vulncheck.com/advisories/frappe-before-15.86.0-ldap-injection-via-unsanitized-endpoint-parameters for additional detail.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic LDAP injection (CWE-90) in the Frappe web framework's LDAP integration layer. Frappe can be configured to use an external LDAP directory for authentication and user/directory lookups; certain HTTP endpoints pass caller-supplied parameters directly into LDAP search filters without escaping or sanitizing LDAP metacharacters such as parentheses, asterisks, pipes, and ampersands. By injecting these characters, a remote attacker can restructure the resulting filter expression, for example broadening a search to match unintended entries or bypassing a conjunctive condition within a query the application already issues. The CPE string cpe:2.3:a:frappe:frappe:*:*:*:*:*:*:*:* indicates the Frappe application package itself is the affected artifact across all tracked versions within the fixed ranges. The impact is deliberately narrow: the query manipulation is confidentiality-oriented, so the assessed effect is limited information disclosure from the directory rather than authentication bypass with privilege escalation, data modification, or denial of service.
Know when Frappe gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Remote unauthenticated (AV:N/PR:N) but AC:H reflects the required LDAP-enabled configuration (AT:P in 4.0); impact is confidentiality-only (C:L) with no integrity or availability effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
Frappe before 14.99.2 and 15.x before 15.86.0 contains an LDAP injection vulnerability because certain endpoints do not sanitize user-supplied parameters before using them in LDAP queries. Attackers can supply crafted LDAP filter syntax through these parameters to alter the resulting directory queries.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Stored cross-site scripting leading to code execution in Frappe Framework 15.89.0 (and the ERPNext application built on
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
Authenticated SQL injection in Frappe ERPNext through 15.89.0 allows low-privilege users to extract arbitrary database c
SQL injection in Frappe ERPNext through 15.89.0 lets an authenticated attacker with a valid session and access to the Pa
Authenticated server-side template injection in Frappe ERPNext through 15.89.0 lets a user who can create or modify an A
An SQL injection vulnerability exists in the frappe.desk.reportview.get functionality of ERPNext 11.1.38. Rated high sev
Arbitrary file read in the Frappe full-stack web application framework allows remote unauthenticated attackers to retrie
SQL injection in Frappe HelpDesk 1.14.0 dashboard functionality allows authenticated attackers to execute arbitrary SQL
In Frappe ERPNext 15.57.5, the function get_rfq_containing_supplier() at erpnext/buying/doctype/request_for_quotation/re
EUVD-2025-211073
GHSA-4wwr-6qhv-m4v4
NVD
CVE.org
EPSS
Exploit-DB