CVE-2026-124313 Frappe ERPNext before 15.121.4 and 16.36.0 Missing Authorization via get_linked_payments_for_doc
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-124313 and fix it if it is affected.
What it is: CVE-2026-124313 is a medium-severity vulnerability in frappe erpnext, published on 7 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124313 exists.
Affected product: frappe erpnext. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-124313/ (Markdown: https://insights.sbomify.com/CVE-2026-124313/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-124313?
CVE-2026-124313 is a medium-severity vulnerability in frappe erpnext, published on 7 Nov 2026.
Official description
Frappe ERPNext before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in the whitelisted get_linked_payments_for_doc method. Any authenticated user, including portal users, can supply arbitrary company, doctype, and docname values to read Payment Ledger Entry allocation data for other companies' invoices and vouchers.
Weakness: CWE-862
Which versions are affected by CVE-2026-124313?
How do I fix CVE-2026-124313?
No fix has been published for CVE-2026-124313 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-124313 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124313 exists.
Sources
Also known as GHSA-c3m9-x4pg-4p8g, GHSA-hf2q-xhq6-q394.