Skip to content

GHSA-vwqr-4mjv-ffrm

Frappe Framework email endpoints allow unauthorised sender spoofing (GHSA-vwqr-4mjv-ffrm)

High 8.5 Vendor: Frappe / ERPNext Published

Frappe Framework before 15.127.1 and 16.0.0 to before 16.60.1 has a high-severity authorisation flaw (GHSA-vwqr-4mjv-ffrm). Any authenticated user, including a Website User, can send email as another sender. Upgrade to 15.127.1 or 16.60.1; no workaround exists.

What happened

Certain Frappe Framework endpoints related to email communication did not enforce proper authorisation checks. An existing check could be satisfied by users who were not meant to send email from the site. Frappe's advisory states that validation was added to restrict sending to permitted users. The flaw is reachable over the network and requires only a low-privilege authenticated account; no user interaction is needed. The CVSS 3.1 score is 8.5, rated high.

An authenticated user with minimal privileges, including a Website User, can send a crafted request to an affected endpoint. The user can then send email through the site's configured email account and make it appear to come from another sender. That capability could be used for spam or phishing in the organisation's name. The advisory also notes that the flaw could expose some files the user is not permitted to access.

Who is affected

The affected product is Frappe Framework. The advisory lists two affected ranges: version 16.0.0 up to before 16.60.1, and versions before 15.127.1. Frappe Framework underpins many ERPNext and other Frappe-based deployments, so teams should confirm the framework version behind their applications, not only the application version. Because the flaw is reachable by any authenticated user, deployments with many low-privilege accounts have a larger exposure.

What to do now

  1. Determine the Frappe Framework version in each deployment.
  2. Upgrade to 16.60.1 for installations in the 16.0.0 to before 16.60.1 range.
  3. Upgrade to 15.127.1 for installations on versions before 15.127.1.
  4. Do not rely on a workaround; Frappe's advisory states that no workaround is available and upgrading is required.

How to detect it

Frappe's advisory does not publish endpoint- or file-level indicators. Because the flaw allows any authenticated user to send email through the configured account, outbound email and gateway logs are the most relevant telemetry to review for unexpected senders, spoofed sender addresses, or unusual volumes triggered by low-privilege accounts.

Beyond the patch

Apply the patch first; this is an authorisation flaw in a web application layer that can turn a low-privilege account into a sender for your domain. If the deployment exposes login to customers or suppliers, an implementation assessment and hardening review can test which authenticated roles can reach sensitive endpoints such as email-sending functions. Frappe Framework is also a third-party component in the ERPNext estate, so its patch cadence and your tracking of affected versions belong in supply-chain risk management.

Affected and fixed versions

ProductAffectedFixed in
Frappe Framework16.0.0 – < 16.60.1
– < 15.127.1
16.60.1
15.127.1
1

References

Sources: the CVE record (MITRE), NVD, CISA KEV and SSVC, ENISA EUVD, FIRST EPSS and the vendor's own advisory. Scores and dates are shown as those sources publish them. Entries marked GHSA have no CVE: their source is the security advisory the maintainers published in their official GitHub repository.

Written with AI assistance from the sources above and checked automatically against them before publication.