CVE-2026-72910

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.22.0, the merge_account, pause_job_for_doc, trigger_job_for_doc, change_release_date, and update_cost_center functions across erpnext/accounts/doctype/account/account.py, erpnext/accounts/doctype/process_payment_reconciliation/process_payment_reconciliation.py, erpnext/accounts/doctype/purchase_invoice/purchase_invoice.py, and erpnext/accounts/utils.py omit required write permission checks, allowing authenticated limited users to modify protected data beyond their roles. This issue is fixed in versions 15.112.0 and 16.22.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 (7)

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

Unauthorised modification of data due to missing validation · Advisory · frappe/erpnext · GitHub

https://github.com/frappe/erpnext/security/advisories/GHSA-qpvh-75wh-j645
github_release Patch Available

v16.22.0

Patch available: frappe/erpnext v16.22.0

https://github.com/frappe/erpnext/releases/tag/v16.22.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: Add authorization checks on internal functions

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

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

commit ba936eefabb7 (frappe/erpnext)

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

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

commit 8c7a313a38df (frappe/erpnext)

Fix landed in frappe/erpnext commit 8c7a313a38df — awaiting tagged release

https://github.com/frappe/erpnext/commit/8c7a313a38dfe38c9e35ca41e91389bcfaed2404
github_commit

commit 2ae6451f1092 (frappe/erpnext)

Fix landed in frappe/erpnext commit 2ae6451f1092 — awaiting tagged release

https://github.com/frappe/erpnext/commit/2ae6451f10926bd12b6ce6c7dc40f08da83f2460

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 16:40 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 02:45 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-26 00:31 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 22:09 UTCEG score recompute
  11. 2026-08-23 06:47 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 04:30 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 02:16 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-19 23:55 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 21:39 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-17 19:17 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 16:44 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:38 UTCEG score recompute
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 14:31 UTCEG score recompute
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-13 23:08 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 20:54 UTCEG score recompute
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 18:40 UTCEG score recompute
  11. 2026-08-11 17:45 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

Frequently asked(5)

What is CVE-2026-72910?
CVE-2026-72910 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.22.0, the mergeaccount, pausejobfordoc, triggerjobfordoc, changereleasedate, and updatecostcenter functions across erpnext/accounts/doctype/account/account.py,…
When was CVE-2026-72910 disclosed?
CVE-2026-72910 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-72910 actively exploited?
CVE-2026-72910 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 80.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72910?
CVE-2026-72910 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-72910?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72910, 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-72910

Explore →

Is Your Infrastructure Affected by CVE-2026-72910?

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