CVE-2025-52044: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
Organizations should immediately audit their ERPNext installations to identify if version 15.57.5 or vulnerable versions are in use. Until an official patch is released, it is recommended to implement the following mitigations: 1) Apply strict input validation and sanitization on the inventory_dimensions_dict parameter at the application or database query layer to prevent injection of malicious SQL code. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the vulnerable endpoint. 3) Restrict network access to the ERPNext application to trusted IP ranges and enforce strong authentication mechanisms to reduce exposure. 4) Monitor database query logs and application logs for unusual or suspicious queries indicative of injection attempts. 5) Prepare for rapid deployment of official patches once available and test updates in a staging environment before production rollout. 6) Consider database-level protections such as using least privilege accounts for the ERPNext application to limit data exposure in case of exploitation.
Description
In Frappe ERPNext v15.57.5, the function get_stock_balance() at erpnext/stock/utils.py is vulnerable to SQL Injection, which allows an attacker to extract all information from databases by injecting SQL query into inventory_dimensions_dict parameter.