TL;DR
On November 19, 2026, Frappe maintainers patched a high-severity Frappe authorization flaw. Threat actors are already exploiting this mail abuse bug in the wild. Site admins must upgrade to Frappe 15.127.1 or 16.60.1 right away.
Why It Matters
Frappe Cloud Marketplace reports serving 28,673 active Frappe sites worldwide. Furthermore, GitHub shows over 11,100 stars for Frappe Framework and 41,400 stars for ERPNext across 30 countries. Because firms run portals and mail flows on Frappe, unpatched sites face sharp phishing risks.
In the official Frappe security advisory, maintainers confirm live attacks. Specifically, the advisory warns: “This could be used for spam or phishing in the organisation’s name, and could expose some files the user is not permitted to access. This flaw has been exploited in the wild.”
How the Attack Works
Missing Sender Checks
This Frappe authorization flaw (CWE-863, CVSS 8.5) stems from weak checks on email endpoints. Maintainers note: “Any authenticated user, including a Website User, could send email through the site’s configured email account and make it appear to come from another sender.”
Consequently, low-level portal users bypass sender rules and forge internal or external emails. They can also attach private files from the host.
Affected Versions
The bug hits Frappe Framework builds prior to 15.127.1 and versions 16.0.0 through 16.60.0. Both self-hosted and cloud apps running older code face risk. No CVE ID has been assigned yet.
Patch and Mitigation Steps
Frappe states that no workaround exists for this Frappe authorization flaw. Therefore, admins must update right away to Frappe 15.127.1 or 16.60.1 and check mail logs for fake emails.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!