CVE-2026-134372
Frappe ERPNext Selling and Buying modules SQL injection lets authenticated users take over accounts (CVE-2026-134372)
ERPNext 4.3.0 before 15.121.6 and 16.x before 16.37.0 has an SQL injection flaw in the Selling and Buying modules. Any authenticated portal user can extract session data and take over accounts. Upgrade to erpnext 15.121.6 or 16.37.0.
What happened
CVE-2026-134372 is an SQL injection weakness in an endpoint of ERPNext's Selling and Buying modules. A request value that is validated early in processing can be overridden by caller-supplied data, and that data then reaches a database query without a second validation step. An attacker who sends a crafted request can therefore alter the logic of the query instead of supplying ordinary input.
The flaw is reachable over the network, requires only a low-privilege authenticated account, and does not need any user interaction. Any authenticated user, including a portal user with no roles, can exploit it. Successful exploitation lets an attacker extract sensitive data, including active session data, and use that to take over other accounts, including administrator accounts. CVSS 4.0 rates the vulnerability 8.3, high, with the main impact on confidentiality. No exploitation or public disclosure is recorded for this CVE.
Who is affected
Affected products are erpnext releases 4.3.0 up to but not including 15.121.6, and 16.0.0 up to but not including 16.37.0. Organisations running ERPNext as their core operational and financial platform should check module usage and portal access first: the flaw sits in the Selling and Buying modules, and the minimum requirement for exploitation is any authenticated session, including a portal user account with no roles assigned. This makes exposure broader than a typical SQL injection that requires an administrative or privileged user.
What to do now
- Upgrade to a fixed release. If you are on a version below 15.121.6, upgrade to erpnext 15.121.6. If you are on a 16.x version below 16.37.0, upgrade to erpnext 16.37.0.
- No workaround is listed in the available sources; the fixed versions are the only releases named as remediating this flaw.
- If you cannot patch immediately, reduce exposure by restricting network access to the ERPNext application and treating authenticated portal sessions as untrusted until the upgrade is complete.
Beyond the patch
After patching, use this as a reason to test the instance, not just patch it. Injection and authentication flaws are precisely what penetration testing and hardening finds before an attacker does, and an ERPNext portal account should not be able to read administrative sessions. At the same time, track Frappe's patch cycle through supply-chain risk management so the delay between a vendor fix and your own upgrade is visible and owned, rather than discovered after an incident.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| erpnext | 4.3.0 – < 15.121.6 | 15.121.6 16.37.0 |
| erpnext | 16.0.0 – < 16.37.0 | 15.121.6 16.37.0 |