CVE-2025-66439: erpnext · SQL Injection
Affects erpnextSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfrappe/erpnextpkg:github/frappe/erpnextOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Monitor Frappe ERPNext official channels for security patches addressing CVE-2025-66439 and apply them immediately upon release.
- Until patches are available, implement strict input validation on the from_posting_date parameter to reject any suspicious or malformed input that could contain SQL syntax.
- Modify the source code to use parameterized queries or prepared statements instead of direct string interpolation for SQL commands, eliminating injection vectors.
- Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint.
- Conduct thorough code audits and penetration testing focusing on database query handling in ERPNext modules.
- Restrict network access to ERPNext instances to trusted IPs and use VPNs or other secure access methods to reduce exposure.
- Enable detailed logging and monitoring of database queries and application logs to detect anomalous activities indicative of exploitation attempts.
- Educate development and operations teams about secure coding practices and the risks of SQL injection vulnerabilities.
Description
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 from_posting_date parameter, which is directly interpolated into the query without proper sanitization or parameter binding.