CVE-2026-72909

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ERPNext is a free and open source Enterprise Resource Planning tool. Prior to 15.112.0 and 16.23.0, the ReceivablePayableReport prepare_conditions path in erpnext/accounts/report/accounts_receivable/accounts_receivable.py does not apply Customer and Supplier user permissions to the Payment Ledger Entry dynamic-link party field, allowing any authenticated user to read unauthorized cross-company financial data in Accounts Receivable and Accounts Payable reports. This issue is fixed in versions 15.112.0 and 16.23.0.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 11, 2026

Advisory Details (6)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Broken Access Control on certain endpoints · Advisory · frappe/erpnext · GitHub

https://github.com/frappe/erpnext/security/advisories/GHSA-p577-cxv9-h82f
github_release Patch Available

v16.23.0

Patch available: frappe/erpnext v16.23.0

https://github.com/frappe/erpnext/releases/tag/v16.23.0
github_release Patch Available

v15.112.0

Patch available: frappe/erpnext v15.112.0

https://github.com/frappe/erpnext/releases/tag/v15.112.0
github_pr

fix: apply user permissions to receivable/payable reports

Fix merged in frappe/erpnext PR #55696 on 2026-06-11 — awaiting tagged release

https://github.com/frappe/erpnext/pull/55696
github_commit

commit c03a66a1bf48 (frappe/erpnext)

Fix landed in frappe/erpnext commit c03a66a1bf48 — awaiting tagged release

https://github.com/frappe/erpnext/commit/c03a66a1bf48a53c42d01c9d936d9b22aa013e11
github_commit

commit b05abbc53b36 (frappe/erpnext)

Fix landed in frappe/erpnext commit b05abbc53b36 — awaiting tagged release

https://github.com/frappe/erpnext/commit/b05abbc53b3655b02db17ba2e8165519f195c1c2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 09:53 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 22:29 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 22:08 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 21:06 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 20:46 UTCEG score recompute
  11. 2026-08-23 07:55 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 07:35 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 07:13 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-19 18:42 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 17:24 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-17 16:30 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 16:05 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 14 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 03:55 UTCEG score recompute
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 03:35 UTCEG score recompute
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 03:14 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 14:44 UTCEG score recompute
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 14:24 UTCEG score recompute
  11. 2026-08-11 13:32 UTCEG score recompute
  12. 2026-08-10 21:31 UTCEG score recompute
  13. 2026-08-10 21:15 UTCEG score recompute
  14. 2026-08-10 21:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72909?
CVE-2026-72909 is a high vulnerability published on August 10, 2026. ERPNext is a free and open source Enterprise Resource Planning tool. Prior to 15.112.0 and 16.23.0, the ReceivablePayableReport prepareconditions path in erpnext/accounts/report/accountsreceivable/accounts_receivable.py does not apply Customer and Supplier user permissions to the Payment Ledger…
When was CVE-2026-72909 disclosed?
CVE-2026-72909 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72909 actively exploited?
CVE-2026-72909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72909?
CVE-2026-72909 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-72909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72909, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72909

Explore →

Is Your Infrastructure Affected by CVE-2026-72909?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs