ERPNext November security advisories require different patch priorities even though the vendor published them together on November 6, 2026. Start with the Selling and Buying SQL injection. Frappe says a portal user without assigned roles could extract active session data and take over other accounts, including administrator accounts.
The 21 CVE records below were published on November 21, after the vendor advisories. They describe different data exposure and integrity risks. One companion row concerns the Frappe framework rather than ERPNext. Check both running package versions and feature access before applying the matrix.
ERPNext November Security Advisories: Patch Priority Matrix
| Issue | Access condition | Effect | CVSS 3.1 | First patched version |
|---|---|---|---|---|
| CVE-2026-134372: Selling/Buying SQL injection | Portal or other login, no assigned role needed | Session data; account takeover | 7.7 | 15.121.6 / 16.37.0 |
| CVE-2026-134378: Supplier e-invoice files | No login; Italian supplier e-invoice import used | Imported invoice files public | 5.3 | 15.124.0 / 16.52.0 |
| CVE-2026-134389: Payment Requests | Accounts User login | Out-of-scope source document emailed | 8.5 | 15.124.0 / 16.52.0 |
| CVE-2026-134393: BOM replacement | Login able to create BOM Update Log | Site-wide BOM replacement | 7.7 | 15.122.0 / 16.50.0 |
| CVE-2026-134388: CRM notes XSS | Sales User login; another user opens record | Script acts with reader permissions | 5.4 | 15.124.0 / 16.52.0 |
| CVE-2026-134377: Projects Timesheets | Any login, no Projects role needed | Work and billing data read | 5.0 | 15.121.0 / 16.34.0 |
| CVE-2026-134373: Bulk transaction retry | Any login, including roleless portal account | Failed logs marked retried | 5.4 | 15.121.0 / 16.34.0 |
| CVE-2026-134376: Invoice subscriptions | Any login | Out-of-scope plan details read | 5.0 | 15.122.0 / 16.34.0 |
| CVE-2026-134375: Payment Entries | Accounts role with record restrictions | Hidden entry metadata read | 5.0 | 15.124.0 / 16.52.0 |
| CVE-2026-134379: Work Orders | Manufacturing write role with record restrictions | Other-company status changed | 4.3 | 15.121.4 / 16.36.0 |
| CVE-2026-134374: Asset depreciation | Any login | Other-company schedules read | 5.0 | 15.124.0 / 16.52.0 |
| CVE-2026-134383: Ledger reposting | Login with voucher read access | Ledger entries reposted | 4.3 | 15.122.0 / 16.50.0 |
| CVE-2026-134385: Tax Rule addresses | Any login, including roleless portal account | Out-of-scope addresses read | 5.0 | 15.122.0 / 16.50.0 |
| CVE-2026-134382: Sales Orders | Selling write role with record restrictions | Other-company status changed | 4.3 | 15.121.4 / 16.36.0 |
| CVE-2026-134386: Inter-company items | Any login, including roleless portal account | Other-company item rows read | 5.0 | 15.121.4 / 16.36.0 |
| CVE-2026-134381: Purchase Orders | Buying write role with record restrictions | Other-company status changed | 4.3 | 15.121.4 / 16.36.0 |
| CVE-2026-134387: Account balance chart | Any login, including roleless portal account | Other-company balance history read | 5.0 | 15.121.4 / 16.36.0 |
| CVE-2026-134384: Stock cost | Any login, including roleless portal account | Item valuation and purchase cost read | 5.0 | 15.124.2 / 16.53.0 |
| CVE-2026-134391: Asset details | Any login, including roleless portal account | Out-of-scope asset details read | 5.0 | 15.122.0 / 16.50.0 |
| CVE-2026-134390: POS Invoice Merge Logs | Any login | Out-of-scope merge log created | 5.0 | 15.122.0 / 16.50.0 |
| CVE-2026-134371: Frappe framework: Frappe Contact number API | Permission check absent; access condition unstated | Contact phone data read | Not stated | 16.30.0 |
The ERPNext advisories give CVSS 3.1 scores and provide no CVSS 4.0 scores. The companion Frappe framework advisory does not state a numeric score. Each version pair is the threshold for that row, not a universal minimum for all November findings.
Frappe’s broader authorisation advisory covers several additional endpoints and says its complete fixes are present in 15.124.2 and 16.53.0. ERPNext teams addressing the reviewed authorization set should plan around those later thresholds, then confirm the exact versions running. The separate Frappe framework row has its own threshold.
Why Does Session Exposure Lead the Queue?
Frappe says a value validated early in processing could be replaced before it reached a database query. Validation was added after the replacement. The resulting SQL injection needs a login, but even a portal user without assigned roles meets that condition.
The vendor says the flaw could expose active session data and allow takeover of other accounts without victim interaction. That makes a broad portal account base relevant to triage. Our priority order is a defensive judgment based on the stated impact and access conditions, not a vendor ranking.
Prioritize internet-reachable ERPNext instances and those with portal accounts. An external attack surface management inventory can help identify exposed application instances and owners. For the broader patch queue, review Vulnerability Intelligence; the application team still verifies deployed versions and roles.
Brandefense Blackhole counted 156 ERPNext-related dark-chat posts from August 23 through November 21, 2026. The unit is matching discussion posts, not unique actors, affected installations, or exploitation of these CVEs. Treat the count as background interest when choosing monitoring coverage, not as proof of an incident.
How Do the Other Preconditions Change Triage?
The invoice-file advisory has a narrower feature condition but no login requirement. Frappe says the Italian supplier e-invoice import saved files publicly, and the fix stores new imports privately. Teams that used this feature should inspect historical file exposure as well as upgrading; the advisory does not say that an upgrade retroactively makes old public files private.
The Timesheet flaw could reveal organisation-wide billing data to any logged-in user. The bulk retry flaw could mark failed transactions as retried and add background job load. Neither advisory says those actions grant access to active sessions, so their response checks differ from the Selling and Buying issue.
The CRM issue requires a Sales User to save a malicious note and another user to open the Lead or Opportunity. Frappe says the note bypassed normal HTML sanitisation and could run script with the reader’s permissions. That is a stored cross-site scripting path with victim interaction, unlike the session-data exposure.
Which Build and Records Should Defenders Check?
Record each deployed ERPNext version, branch, exposed site, portal-account population, and use of Italian supplier e-invoice imports. Upgrade to a release containing the complete fixes for the features in use. Frappe lists no workaround for the selected advisories, so access restrictions are temporary risk reduction rather than a replacement for updating.
After deployment, verify the running version on each site. Review authentication and session records around unexpected account activity, especially portal accounts followed by privileged sessions. Correlate application logs with user and time context before drawing conclusions, because a login or a database error alone does not establish exploitation.
For invoice imports, check whether previously imported files remain publicly reachable and handle confirmed exposure under the organisation’s data-response process. For Timesheets and bulk retries, inspect out-of-scope reads and unusual retry activity where audit data exists. For CRM notes, review suspicious note edits and affected record access, then verify that sanitisation applies in the patched build.
Use a vulnerability management process to capture deployment evidence, owners, and follow-up checks. These are our recommended validation steps derived from the vendor’s described impacts. The advisories establish the flaws and fixed versions; local logs establish whether a particular site experienced suspicious activity.
Frequently Asked Questions
Which ERPNext versions address the full reviewed advisory set?
Frappe lists 15.124.2 and 16.53.0 as containing all fixes in its broader authorization advisory. Check each selected advisory for its own earlier threshold.
Does the session exposure require administrator access?
No. Frappe says any authenticated account, including a portal account without assigned roles, can reach the Selling and Buying flaw.
Can an upgrade alone secure old public supplier invoices?
The advisory says new imports are stored privately after the fix. It does not establish that previously public files are retroactively protected; check historical exposure.
Sources
- Frappe ERPNext: Selling and Buying SQL injection
- Frappe ERPNext: public supplier e-invoices
- Frappe ERPNext: Projects Timesheet authorization
- Frappe ERPNext: Utilities bulk transaction retry
- Frappe ERPNext: stored CRM notes XSS
- Frappe ERPNext: broader authorization fixes
- CVE Program: CVE-2026-134372 record
