Security readout for executives and security teams
Plain-English summary
An authenticated ERPNext user with a common operational role could abuse statement-template fields to run code on the server. Successful exploitation could expose or alter data across the application and disrupt operations. ERPNext releases 15.118.0 and 16.29.0 fix the issue.
Executive priority
Treat this as an immediate patching priority for affected ERPNext systems, especially internet-accessible or business-critical deployments. The prerequisite is only an authenticated operational account, so compromised credentials or malicious insiders could potentially gain broad control over ERP data and service availability.
Technical view
CVE-2026-72911 is server-side template injection in Process Statement of Accounts. The validate_template and render_template calls process subject, body, and pdf_name with unrestricted globals, including frappe.utils. This enables low-privileged authenticated server-side code execution. CVSS 3.1 is 9.9, with confidentiality, integrity, and availability impacts across scope.
Likely exposure
ERPNext versions below 15.118.0 and versions from 16.0.0 through 16.28.x are identified as affected. Exposure requires an authenticated account with access to the vulnerable Process Statement of Accounts functionality; the advisory indicates a common operational role can satisfy this requirement.
Exploitation context
The attack is network-accessible, requires low privileges, needs no user interaction, and has low stated complexity. The supplied bundle marks KEV as false, and no cited source establishes active exploitation. Public fix commits and pull-request details may nevertheless help attackers analyze the weakness.
Researcher notes
The weakness maps to CWE-1336 and represents a trust-boundary failure during server-side template evaluation. Validation should focus on affected call paths, deployed version provenance, role reachability, stored template content, and evidence of server-side execution. The supplied evidence does not establish exploitation in the wild or provide confirmed indicators of compromise.
Mitigation direction
- Upgrade ERPNext 15 deployments to version 15.118.0 or later.
- Upgrade ERPNext 16 deployments to version 16.29.0 or later.
- Until upgraded, restrict access to the affected Process Statement of Accounts functionality.
- Investigate and isolate affected systems if suspicious template activity or unauthorized data access is found.
Validation and detection
- Inventory every ERPNext deployment and record its exact installed version.
- Confirm each deployment runs 15.118.0, 16.29.0, or a later supported release.
- Identify accounts and roles able to access Process Statement of Accounts.
- Inspect subject, body, and pdf_name values for unexpected template expressions.
- Review application and host telemetry for unexplained server execution or unauthorized data access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1336: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-72911 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/frappe/erpnext/security/advisories/GHSA-qq49-v74j-hjh7CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/frappe/erpnext/pull/56458CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/frappe/erpnext/commit/5f6952b15c1f6ee893770d5bc618558a6ba41a28CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/frappe/erpnext/commit/88443e4a97c6c0a40d85a9e6785577191296ee39CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/frappe/erpnext/commit/ecb6d48ec025e0c94abac35b2e4f7607f4c86465CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/frappe/erpnext/releases/tag/v15.118.0CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/frappe/erpnext/releases/tag/v16.29.0CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements Used in a Template Engine
Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.