Frappe has patched an authorization flaw in the Frappe Framework that its own advisory says has already been exploited in the wild. The bug lets any authenticated user, including a Website User, send email through a site’s configured account while impersonating another sender.
Authorization Flaw Lets Any Logged-In User Send Spoofed Email
The vulnerability is classified as CWE-863, an incorrect authorization weakness, and rated CVSS 8.5. No CVE identifier has been assigned yet. Any authenticated user can send email through the site’s configured mail account while spoofing another sender. The same user can attach private files that they should not be able to access.
Frappe’s advisory states that the flaw has been exploited in the wild. The advisory describes no workaround, so applying the update is the only available remedy.
Affected Versions of Frappe Framework and ERPNext Base
The flaw affects Frappe Framework before version 15.127.1 and releases from 16.0.0 through 16.60.0. Frappe is the base for ERPNext. Patches shipped in versions 15.127.1 and 16.60.1.
Scale of the Frappe Cloud Marketplace Exposure
Frappe Cloud Marketplace lists 28,673 active sites. The reporting does not state how many of those sites are affected or how many were targeted in the exploitation that the advisory acknowledges. The low privilege needed to trigger the bug is the main driver of exposure: a Website User account, the lowest tier of authenticated access, is enough.
Phishing and Spam in an Organization’s Name
The most direct consequence is phishing and spam that arrives in an organization’s name. Because the mail goes out through the victim site’s own configured account, recipients see messages that appear to come from a trusted sender. The attachment weakness adds a second risk, since private files that a user should not reach can be attached to an outgoing message.
Mail Log Review for Forged Messages
The recommended response, beyond upgrading, is to review mail logs for forged emails. That step addresses the possibility that attackers already used the flaw before the patch, which the advisory’s confirmation of in-the-wild exploitation makes plausible. Logs that show messages sent under another user’s identity, or with unexpected attachments, would indicate abuse.
A Low-Barrier Flaw With Confirmed Exploitation
The combination of a low authentication bar, confirmed exploitation and no workaround places pressure on administrators to upgrade quickly. The advisory does not describe who exploited the flaw or against which sites. The patch releases on both supported branches close the weakness, but organizations that ran vulnerable versions have no way to confirm from the advisory alone whether their instance was abused, which is why the log review is the recommended follow-up.
How the Frappe Flaw Differs From a Typical Authentication Bypass
CWE-863 describes an authorization failure: the attacker is already logged in, but the system fails to check what that user is allowed to do. That distinction explains why the lowest tier of account, a Website User, is enough. The flaw has two effects that reinforce each other. Sending email as someone else lets a user build convincing messages through the site’s own mail configuration, and attaching private files lets the same user pull data into those messages that they should not reach. Frappe’s advisory frames the flaw as already exploited, though it does not say how widely or by whom. The unassigned CVE identifier means the vulnerability may not yet appear in scanners that rely on CVE feeds.
The reporting also gives context on scale: the Frappe Cloud Marketplace lists 28,673 active sites. Administrators of ERPNext-based installations should note that the fixed releases are 15.127.1 on the older branch and 16.60.1 on the newer one, and that the advisory offers no workaround for sites that cannot upgrade right away.
