Frappe ERPNext up to 15.89.0 API get_html_and_style special elements used in a template engine
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Frappe ERPNext up to 15.89.0. Affected is the function get_html_and_style of the component API. Such manipulation leads to improper neutralization of special elements used in a template engine.
This vulnerability is referenced as CVE-2025-66438. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Frappe ERPNext up to 15.89.0. It has been rated as critical. Affected by this issue is the function get_html_and_style of the component API. The manipulation with an unknown input leads to a improper neutralization of special elements used in a template engine vulnerability. Using CWE to declare the problem leads to CWE-1336. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. Impacted is confidentiality, integrity, and availability. CVE summarizes:
A Server-Side Template Injection (SSTI) vulnerability exists in the Frappe ERPNext through 15.89.0 Print Format rendering mechanism. Specifically, the API frappe.www.printview.get_html_and_style() triggers the rendering of the html field inside a Print Format document using frappe.render_template(template, doc) via the get_rendered_template() call chain. Although ERPNext wraps Jinja2 in a SandboxedEnvironment, it exposes sensitive functions such as frappe.db.sql through get_safe_globals(). An authenticated attacker with permission to create or modify a Print Format can inject arbitrary Jinja expressions into the html field. Once the malicious Print Format is saved, the attacker can call get_html_and_style() with a target document (e.g., Supplier or Sales Invoice) to trigger the render process. This leads to information disclosure from the database, such as database version, schema details, or sensitive values, depending on the injected payload. Exploitation flow: Create a Print Format with SSTI payload in the html field; call the get_html_and_style() API; triggers frappe.render_template(template, doc) inside get_rendered_template(); leaks database information via frappe.db.sql or other exposed globals.
The advisory is shared for download at notion.so. This vulnerability is handled as CVE-2025-66438 since 11/30/2025. The exploitation is known to be easy. The attack may be launched 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 T1221.
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.
Product
Vendor
Name
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.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper neutralization of special elements used in a template engineCWE: CWE-1336 / CWE-791 / CWE-790
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/30/2025 CVE reserved12/15/2025 Advisory disclosed
12/15/2025 VulDB entry created
01/05/2026 VulDB entry last update
Sources
Advisory: notion.soStatus: Not defined
CVE: CVE-2025-66438 (🔒)
GCVE (CVE): GCVE-0-2025-66438
GCVE (VulDB): GCVE-100-336500
Entry
Created: 12/15/2025 21:32Updated: 01/05/2026 19:56
Changes: 12/15/2025 21:32 (53), 01/05/2026 19:56 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.