Frappe Email Flaw GHSA-vwqr-4mjv-ffrm Exploited: Any Logged-In Website User Could Send Phishing Through Your ERPNext Mail Server and Attach Private Files — Update to 15.127.1 or 16.60.1

Cyber · 2026-11-21 · By H.A

Frappe Email Flaw GHSA-vwqr-4mjv-ffrm Exploited: Any Logged-In Website User Could Send Phishing Through Your ERPNext Mail Server and Attach Private Files — Update to 15.127.1 or 16.60.1

Frappe's maintainers confirm in-the-wild exploitation of a CVSS 8.5 authorization flaw in email.make that let any authenticated user, including self-registered portal users, send spoofed email through the organisation's mail account and attach files they should not see; there is no workaround, so upgrade to 15.127.1 or 16.60.1.

What Happened

The maintainers of Frappe Framework, the open-source Python platform behind ERPNext, Frappe HR, Helpdesk, LMS and many custom business portals, have published a high-severity advisory, GHSA-vwqr-4mjv-ffrm. It covers a broken authorization check in the email communication feature. The advisory states plainly: "This flaw has been exploited in the wild."

The bug lets any logged-in user, including a low-privilege Website User, send email through the organisation's own configured mail account and make it look as if it came from another sender. The advisory says it can be used "for spam or phishing in the organisation's name" and that it "could expose some files the user is not permitted to access."

The fixed releases, Frappe 15.127.1 and 16.60.1, went out on 18 November at 01:32 and 01:54 Mauritius time (17 November, 21:32 and 21:54 UTC). The advisory followed on 19 November. GitHub rates it CVSS 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N) and classes it as CWE-863, Incorrect Authorization. No CVE ID had been assigned when we checked. The maintainers say there is no workaround and upgrading is the only fix.

Technical Details

The vulnerable code is frappe.core.doctype.communication.email.make, a whitelisted server method. That means any authenticated session can call it over Frappe's standard /api/method/ interface. It is the method behind the "New Email" dialog that staff use to send a quotation, invoice or reply straight from a document.

The pre-patch code in 15.127.0 shows why it was so easy to abuse:

The advisory's own wording is that "an existing authorization check could be satisfied by users who were not meant to send email from the site." In other words, the check that existed was too weak for the job.

The fix, merged as pull request #47833 (15.x) and #47834 (16.x), adds one line of policy before anything else runs. If the caller is not a System User (Frappe's term for staff accounts with desk access), the request fails with "Not permitted". The pull request says simply: "Website Users have no need for this."

We are not publishing request details. The advisory's proof-of-concept is one sentence: a minimally privileged authenticated user sends a crafted request to the affected endpoint.

Who Is Affected

Patch Status

The patches are out. Update to Frappe 15.127.1 or 16.60.1 (or later). Self-hosted bench installations can update with the usual workflow:

bench --site all backup
bench update
bench version   # confirm frappe 15.127.1+ or 16.60.1+

Frappe Cloud customers should check that their bench group is on a release that includes the fix. Where automatic updates are not enabled, deploy one. Forks and vendors that pin Frappe to an older tag need to pick up the backported commit themselves.

What To Do Now

Why It Matters

This isn't a remote-code-execution bug, and that is why it is easy to underrate. Attackers don't need a shell when they can borrow a company's trusted mail server. Phishing sent from an organisation's real infrastructure, with valid authentication and a familiar sender, is far more convincing than anything sent from a lookalike domain. That matters most for ERP systems that routinely email invoices, purchase orders and payment details to customers and suppliers.

The flaw also shows a common pattern in web frameworks. A permission check sits behind a condition ("only if a document was named"), and an internal helper deliberately bypasses permissions on the assumption that the caller has already been vetted. When the outer check can be skipped, the inner trust becomes the vulnerability. Teams that build on Frappe should review their own whitelisted methods for the same shape. Any endpoint that only checks permissions when an optional argument is present deserves a second look.

Sources

REEF SENTINEL