CVE-2025-66437: frappe · n/a
Affects frappeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIfrappepkg:pypi/frappeOther threats | Affected
| Fixed in– |
PyPIerpnextpkg:pypi/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
To mitigate CVE-2025-66437, European organizations should immediately audit and restrict permissions related to creating or modifying Address Templates in ERPNext, ensuring only trusted administrators have such access. Implement strict role-based access controls (RBAC) and regularly review user privileges. Monitor template content for suspicious Jinja expressions or unexpected changes. Apply any available patches or updates from ERPNext vendors promptly once released. If patches are not yet available, consider disabling or restricting the get_address_display API usage or the Address Template feature temporarily. Employ network segmentation and monitoring to detect anomalous API calls or unusual database queries originating from ERPNext servers. Conduct thorough security training for administrators to recognize and prevent unsafe template modifications. Additionally, implement application-layer firewalls or runtime application self-protection (RASP) solutions that can detect and block SSTI attempts. Regularly back up ERP data and test recovery procedures to minimize impact in case of exploitation.
Description
An SSTI (Server-Side Template Injection) vulnerability exists in the get_address_display method of Frappe ERPNext through 15.89.0. This function renders address templates using frappe.render_template() with a context derived from the address_dict parameter, which can be either a dictionary or a string referencing an Address document. Although ERPNext uses a custom Jinja2 SandboxedEnvironment, dangerous functions like frappe.db.sql remain accessible via get_safe_globals(). An authenticated attacker with permission to create or modify an Address Template can inject arbitrary Jinja expressions into the template field. By creating an Address document with a matching country, and then calling the get_address_display API with address_dict="address_name", the system will render the malicious template using attacker-controlled data. This leads to server-side code execution or database information disclosure.