ERPNext: Unauthorised triggering of automated emails due to missing validation
Published Aug 10, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
ERPNext: Unauthorised triggering of automated emails due to missing validation
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
ERPNext is a free and open source Enterprise Resource Planning tool. Prior to 15.111.0 and 16.22.0, the send_auto_email function in erpnext/accounts/doctype/process_statement_of_accounts/process_statement_of_accounts.py lacks a Process Statement Of Accounts permission check, allowing an authenticated low-privilege user to trigger automated emails outside the permitted role. This issue is fixed in versions 15.111.0 and 16.22.0.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Patch commit ↗
- Patch commit ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
- Security advisory ↗
Record history
Published Aug 10, 2026 · Last refreshed Nov 3, 2026