CVE-2025-52047

CVE-2025-52047 is a medium-severity vulnerability in Frappe Erpnext with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Description

In Frappe ErpNext v15.57.5, the function get_income_account() at erpnext/controllers/queries.py is vulnerable to SQL Injection, which allows an attacker to extract all information from databases by injecting a SQL query into the filters.disabled parameter.

Frequently asked questions

What is CVE-2025-52047?
In Frappe ErpNext v15.57.5, the function get_income_account() at erpnext/controllers/queries.py is vulnerable to SQL Injection, which allows an attacker to extract all information from databases by injecting a SQL query into the filters.disabled parameter.
How severe is CVE-2025-52047?
CVE-2025-52047 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-52047 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-52047?
CVE-2025-52047 affects Frappe Erpnext. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-52047?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-52047 have an EU (EUVD) identifier?
Yes. CVE-2025-52047 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31735.
When was CVE-2025-52047 published?
CVE-2025-52047 was published on 2025-09-30 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Frappe Erpnext

All CVEs affecting Frappe Erpnext →

Other CWE-89 (SQL Injection) vulnerabilities

Browse all CWE-89 (SQL Injection) vulnerabilities →