Frappe ERPNext up to 15.89.0 payment_entry.py to_posting_date sql injection

Summaryinfo

A vulnerability, which was classified as critical, was found in Frappe ERPNext up to 15.89.0. This affects an unknown part of the file erpnext/accounts/doctype/payment_entry/payment_entry.py. The manipulation of the argument to_posting_date results in sql injection. This vulnerability is reported as CVE-2025-66440. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical has been found in Frappe ERPNext up to 15.89.0. Affected is some unknown functionality of the file erpnext/accounts/doctype/payment_entry/payment_entry.py. The manipulation of the argument to_posting_date with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

An issue was discovered in Frappe ERPNext through 15.89.0. Function get_outstanding_reference_documents() at erpnext/accounts/doctype/payment_entry/payment_entry.py is vulnerable to SQL Injection. It allows an attacker to extract arbitrary data from the database by injecting SQL payloads via the to_posting_date parameter, which is directly interpolated into the query without proper sanitization or parameter binding.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-66440 since 11/30/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/05/2026). The MITRE ATT&CK project declares the attack technique as T1505.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Frappe

Name

• ERPNext

Version

• 15.0
• 15.1
• 15.2
• 15.3
• 15.4
• 15.5
• 15.6
• 15.7
• 15.8
• 15.9
• 15.10
• 15.11
• 15.12
• 15.13
• 15.14
• 15.15
• 15.16
• 15.17
• 15.18
• 15.19
• 15.20
• 15.21
• 15.22
• 15.23
• 15.24
• 15.25
• 15.26
• 15.27
• 15.28
• 15.29
• 15.30
• 15.31
• 15.32
• 15.33
• 15.34
• 15.35
• 15.36
• 15.37
• 15.38
• 15.39
• 15.40
• 15.41
• 15.42
• 15.43
• 15.44
• 15.45
• 15.46
• 15.47
• 15.48
• 15.49
• 15.50
• 15.51
• 15.52
• 15.53
• 15.54
• 15.55
• 15.56
• 15.57
• 15.58
• 15.59
• 15.60
• 15.61
• 15.62
• 15.63
• 15.64
• 15.65
• 15.66
• 15.67
• 15.68
• 15.69
• 15.70
• 15.71
• 15.72
• 15.73
• 15.74
• 15.75
• 15.76
• 15.77
• 15.78
• 15.79
• 15.80
• 15.81
• 15.82
• 15.83
• 15.84
• 15.85
• 15.86
• 15.87
• 15.88
• 15.89.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion