CVE-2025-58375: Frappe has potential SQL Injection due to missing validation
Frappe is a full-stack web application framework. Versions 14.96.9 and below, and 15.0.0 through 15.71.0 have an insecure endpoint parameter that is vulnerable to error-based SQL Injection through lack of validation. Sensitive information such as versioning can be retrieved. This issue is fixed in versions 14.96.10 and 15.72.0.
Security readout for executives and security teams
Plain-English summary
A network-accessible, low-privileged user may exploit inadequate parameter validation in affected Frappe versions to trigger error-based SQL injection. The flaw can expose sensitive database information and may permit unauthorized data changes. No user interaction is required. The supplied evidence does not establish active exploitation.
Executive priority
Prioritize remediation for internet-facing or broadly accessible Frappe deployments. The combination of network reachability, low required privileges, and possible data disclosure or modification warrants prompt patching. Treat systems containing sensitive or regulated data as the highest priority, while recognizing that active exploitation is not established by the supplied evidence.
Technical view
CVE-2025-58375 is CWE-89 in an unspecified Frappe endpoint parameter. Affected releases are 14.96.9 and earlier, plus 15.0.0 through 15.71.0. CVSS 3.1 is 8.1: network-reachable, low complexity, low privileges, no interaction, with high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Organizations running affected Frappe framework versions are potentially exposed where the vulnerable endpoint is reachable by a low-privileged authenticated user. The bundle does not identify the endpoint, required role, default exposure, or affected applications built on Frappe, so deployment-specific reachability must be verified.
Exploitation context
The documented technique is error-based SQL injection caused by missing parameter validation. Version information can be retrieved, while the CVSS assessment indicates potentially high confidentiality and integrity impact. KEV is false, and the supplied sources provide no evidence of active exploitation. No exploit prerequisites beyond low privileges and network access are specified.
Researcher notes
The bundle does not name the vulnerable endpoint or parameter, limiting precise exposure testing. Review the vendor advisory and referenced fixes to understand the validation change without testing production destructively. Focus defensive investigation on version confirmation, endpoint authorization, application errors, and anomalous low-privileged activity. Do not infer impact to every Frappe-based application without deployment evidence.
Mitigation direction
Upgrade Frappe 14 deployments to version 14.96.10 or later.
Upgrade Frappe 15 deployments to version 15.72.0 or later.
Restrict vulnerable endpoint access until upgrades are completed.
Follow the vendor advisory for deployment-specific remediation guidance.
Validation and detection
Inventory deployed Frappe versions across production and non-production environments.
Confirm no installation remains below 14.96.10 or within 15.0.0 through 15.71.0.
Verify upgraded applications report the intended fixed Frappe version.
Review application and database logs for repeated parameter errors or unusual authenticated requests.
Confirm the vulnerable endpoint is not unnecessarily exposed to low-privileged accounts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.