How many CVEs have patched get_customer_group_condition?

1 published CVEs changed get_customer_group_condition in frappe/erpnext, in 4 distinct patches totalling 8 changed lines, between 2026 and 2026.

What is the latest CVE that changed get_customer_group_condition?

CVE-2026-72908 (ERPNext: Possibility of SQL injection due to missing validation), published 2026-08-10, changed lines 245 of erpnext/accounts/doctype/tax_rule/tax_rule.py.

How does get_customer_group_condition compare to the rest of frappe/erpnext?

frappe/erpnext has 22 CVEs with a located fix in total; 1 of them changed get_customer_group_condition.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

frappe/erpnext

Function

get_customer_group_condition

Name: get_customer_group_condition in frappe/erpnext: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

erpnext/accounts/doctype/tax_rule/tax_rule.py

Last patched August 10, 2026

1

CVEs

That changed this function

4

Distinct patches

Backports counted once

8

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

get_customer_group_condition in frappe/erpnext was changed by 1 published CVE fixes in 2026, in 4 distinct patches that added or removed 8 lines in total.

frappe/erpnext has 22 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed get_customer_group_condition, newest first, with the lines each fix touched.

ERPNext: Possibility of SQL injection due to missing validation
CVE-2026-72908 · line 245 · +0 −8
Medium · CVSS 6.5
EPSS 0.5%2026-08-10

Get an alert when the next CVE fix lands in frappe/erpnext, with the patched functions.

Monitor erpnext CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1get_group_ancestorserpnext/accounts/doctype/tax_rule/tax_rule.py1 CVEs · 4 patches2026

Other hotspots in the repository

Functions in frappe/erpnext changed by the most CVE fixes.

inner_join11 CVEs · erpnext/projects/doctype/timesheet/timesheet.py from_10 CVEs · erpnext/controllers/queries.py get_material_requests_based_on_supplier10 CVEs · erpnext/stock/doctype/material_request/material_request.py select10 CVEs · erpnext/accounts/doctype/loyalty_program/loyalty_program.py get_income_account10 CVEs · erpnext/controllers/queries.py unset_existing_data10 CVEs · erpnext/accounts/doctype/chart_of_accounts_importer/chart_of_accounts_importer.py

All patched functions in frappe/erpnext

Frequently asked questions

Common questions about CVE fixes to get_customer_group_condition.

How many CVEs have patched get_customer_group_condition?: 1 published CVEs changed get_customer_group_condition in frappe/erpnext, in 4 distinct patches totalling 8 changed lines, between 2026 and 2026.
What is the latest CVE that changed get_customer_group_condition?: CVE-2026-72908 (ERPNext: Possibility of SQL injection due to missing validation), published 2026-08-10, changed lines 245 of erpnext/accounts/doctype/tax_rule/tax_rule.py.
How does get_customer_group_condition compare to the rest of frappe/erpnext?: frappe/erpnext has 22 CVEs with a located fix in total; 1 of them changed get_customer_group_condition.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track frappe/erpnext CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing